2026-11-13 20:18:19Dave LeBlanc:
BeeGFS updated on Fri Nov 13 20:18:04 2026
main/beegfs.md ..
@@ 1,1 1,362 @@
# BeeGFS
+
+
A particular need has risen that a research group needs large amounts of storage space, yet reliable and fast.
+
+
Traditionally, central file storage is relatively slow, especially when implemented with NFS, as its designed for availability and reliability and not speed.
+
+
As an option, we've installed additional 14TB drives in a few machines, 7TB drives in a few others, and made those available as an aggregate storage volume that is faster than NFS.
+
The disadvantage is that this architecture requires several services to be up and running else the entire volume/filesystem will become unavailable or unstable.
+
+
After considerable testing and experimentation, BeeGFS tends to perform better than other alternatives, though with the aforementioned downside of required services.
+
For specifics on the testing done, see [Throughput](/Main/BeeGFS#scratch-nfs-write).
+
+
## Implementation
+
We're going off the [BeeGFS Quickstart](https://doc.beegfs.io/latest/quick_start_guide/quick_start_guide.html#example-setup).
+
+
We're installing on Ubuntu 22.04 LTS.
+
First, we'll add the repositories, then we'll add the packages and configure.
+
+
### Repository Keys
+
Since things have changed slightly since the test (below), we need to add the GPG repository key in a different way than is noted in BeeGFS Quickstart.
+
`wget -qOhttps://website/release/GPG-KEY | apt-key add -` will no longer work as it has been DEPRECATED.
Also, edit the `/etc/beegfs/beegfs-client.conf` to include the `connauthfile` directive.
+
Additionally, we'll need the `beegfs-helperd` package installed, and configured via the `/etc/beegfs/beegfs-helperd.conf` file to include the `connauthfile` directive.
+
+
### BeeGFS-MOUNT
+
Finally, each client that will be mounting the filesystem will have a list of mounted and client config files in `/etc/beegfs/beegfs-mount.conf` that looks similar to:
+
+
```
+
/srv/tmp /etc/beegfs/beegfs-client.conf
+
```
+
+
As you guessed it, the system will mount the filesystem onto `/srv/tmp`.
+
+
## Daemon Launch/Enable
+
On `IMAGING-01` (the `-mgmtd` and `-meta` node),
+
Launch:
+
`systemctl start beegfs-mgmtd`
+
`systemctl start beegfs-meta`
+
and check for errors (they may fail silently).
+
+
On all participating nodes (`IMAGING-01 thru -04`)
+
Launch:
+
`systemctl start beegfs-storage`
+
`systemctl start beegfs-helperd`
+
`systemctl start beegfs-client`
+
and check for errors.
+
+
## Checking Validity
+
If everything went as expected, you should be able to verify with some `beegfs-utils` commands ala: