Just to clarify, when I referred to "file level backup/restore", I was
referring to the MDT ldiskfs filesystem, not the whole Lustre filesystem (which
would be _much_ too large for most sites. The various backup/restore methods
are documented in the Lustre Operations Manual.
Cheers, Andreas
This is excellent information, Andreas.
Presently we do file level backups to the live file system and they take
over 24 hours, so they're done continuously. For that timeframe to wrok,
we'd need to be able to back up and recover the MDT to the new MDT with
the file system online.
Given
Normally the easy answer would be that a "dd" copy of the MDT device from your
HDDs to a larger SSD LUN, then resize2fs to increase the filesystem size would
also increase the number of inodes proportionately to the LUN size.
However, since you are *not* using 1024-byte inode size, only
Hi everyone,
One of our lustre file systems outgrew its MDT and the original scope of
its operation. This one is still running ldiskfs on the MDT. Here's our
setup and restrictions:
- centos 6 / lustre 2.8
- ldiskfs MDT
- minimal downtime allowed, but the FS can be read-only for a while.
