BeeGFS v7.4.0 Upgrade Guide¶
Please read and understand the information below completely before attempting the upgrade.
Possible upgrade paths¶
- The following upgrade paths from older versions are supported:
v2014.01 ⟶ v6.19 ⟶ v7.4.0
v2015.03 ⟶ v6.19 ⟶ v7.4.0
v6.x ⟶ v7.4.0
v7.x ⟶ v7.4.0
When upgrading from v2014.01 or v2015.03, an intermediate step is required. Upgrade to v6.19 by following the upgrade instructions in the Wiki under https://www.beegfs.io/wiki and/or the respective upgrade notes under https://www.beegfs.io/release. After that, start the management daemon at least once. You can then proceed with procedure below.
Upgrade to v7.4.0¶
Note
A backup of the system after stopping all services and before upgrading packages from versions older than 7.4.0 is recommended.
Warning
All buddies have to be in the GOOD
state before upgrading to this release.
If you use buddy mirroring, make sure that all buddies are in
GOOD
state.- Stop the BeeGFS system:
stop/unmount all clients
stop all storage daemons
stop all meta daemons
stop the management daemon
Create a full BeeGFS backup if possible, backup the configuration files of all servers (see Backup).
Upgrade all BeeGFS packages.
Check the configuration files. Some configuration options are no longer valid and have to be removed (see Release Notes v7.4.0).
Start all daemons and clients and verify that the system works as expected.
Hard links migration¶
The following BeeGFS components have been changed to add support for cross-directory hard links:
beegfs-client
beegfs-meta
beegfs-fsck
beegfs-ctl
If there are hard links (same directory) present in you BeeGFS file system, they should be migrated to the new de-inlined format (more information on that in the 7.4.0 Release Notes). If not migrated, old-style hard links will continue to work, but they can’t be moved because their on-disk formats are still use inlined inodes. Hard links created in version 7.4.0 will always use the new format.
To facilitate migration, we have introduced a new beegfs-fsck --checkfs
mode called
checkAndUpdateOldStyledHardlinks
that can be used to detect and migrate old-style hard links to
the new format. We recommend the following procedure:
Upgrade system to version 7.4.0 and start all BeeGFS server services.
Ideally, leave clients offline until the migration is finished. This is not strictly necessary, but we recommend against running
beegfs-fsck
repair operations other than migrating the hard link format while the file system is online.Run
beegfs-fsck --checkfs --checkOldStyledHardlinks --readonly
to check if a migration is necessary. If no old-style hard links are found, the file system is ready to go.- If old-style hardlinks are detected, you have two options:
Either rerun
beegfs-fsck --checkfs --checkOldStyledHardlinks
without the--readonly
flag and choose “Update metadata…” for all files.Or remove all but one of the links for each file that is found and recreate hard links using
ln
. They will automatically be created in the new format.
After
beegfs-fsck
finishes without errors, the file system can be opened up to clients again. All hard links will now use the new format.