Luster User Guide section 15.2
"If hardware replacement is the reason for the backup or if a spare
storage device is
available, it is possible to do a raw copy of the MDS or OST from one
block device to
the other, as long as the new device is at least as large as the
original device. To do
this
So your new MDT volume had the same size as the old one? You didn't have to
resize?
Would be interesting to know if someone has experience with resize2fs applied
to a MDT ...
Cheers,
Thomas
On 02/03/2011 06:35 PM, Bob Ball wrote:
> We used dd. It took about 12 hours. After the dd, we did an
On 2011-02-01, at 11:38, Jason Rappleye wrote:
> I heard through the grapevine that you suggest not using "too few" flex_bgs
> on an ext4 filesystem. Can you elaborate on what might be a reasonable
> number, and why?
My gut feeling is that a flex_bg factor of 256 may give the best tradeoff of
We used dd. It took about 12 hours. After the dd, we did an e2fsck on
the new volume, remounted it as the MDT, and Lustre happily began
serving files again.
Thanks to everyone for their help.
bob
On 2/3/2011 12:21 PM, Frederik Ferner wrote:
> Bob Ball wrote:
>> Is there a recommended way to
Bob Ball wrote:
> Is there a recommended way to migrate an MDT (MGS is separate) volume
> from one location to another on the same server? This uses iSCSI volumes.
>
> Lustre 1.8.4
We have recently migrated our MDT to an new volume to change the inode
size. We used tar and getfattr/setfattr fo
On 02.02.2011 18:15, Bob Ball wrote:
> Is there a recommended way to migrate an MDT (MGS is separate) volume
> from one location to another on the same server? This uses iSCSI volumes.
>
> Lustre 1.8.4
>
We'll try the copy (DRBD) + resize variant soon. I've tried that with a
backup copy of the M
