[Top] [All Lists]

RE: mkfs.xfs created filesystem larger than underlying device

To: Linux XFS <xfs@xxxxxxxxxxx>
Subject: RE: mkfs.xfs created filesystem larger than underlying device
From: pg_xf2@xxxxxxxxxxxxxxxxx (Peter Grandi)
Date: Sat, 27 Jun 2009 12:33:44 +0100
In-reply-to: <98D6DBD179F61A46AF5C064829A832A0185042D265@xxxxxxxxxxxxxxxxxxxxxxx>
References: <98D6DBD179F61A46AF5C064829A832A0185042D261@xxxxxxxxxxxxxxxxxxxxxxx> <4A42A7B7.3040403@xxxxxxxxxxx> <98D6DBD179F61A46AF5C064829A832A0185042D265@xxxxxxxxxxxxxxxxxxxxxxx>
>> I recently created an XFS filesystem on an x86_64 CentOS 5.3
>> system.[ .. ] It is a somewhat complex configuration of:

>> Areca RAID card with 16 1.5TB drives in a RAID 6 with 1
>> hotspare (100GB volume was created for the OS, the rest was
>> one large volume of ~19TB)
>> I used pvcreate /dev/sdb to create a physical volume for LVM
>> on the 19TB volume.
>> I then used vgcreate to create a volume group of 17.64TB
>> I used lvcreate to create 5 logical volumes, 4x4TB, and 1x1.5TB
>> On top of those logical volumes is drbd (/dev/drbd0-/dev/drbd4)
>> On top of the drbd volumes, I created a volume group of 17.50TB
>> (/dev/drbd0-/dev/drbd4)
>> I created a logical volume of 17.49TB, upon which was created
>> an xfs filesystem with no options (mkfs.xfs mkfs.xfs
>> /dev/Volume1-Rep-Store/Volume1-Replicated -L Replicated)

One of the values of the XFS mailing list is the entertainment
provided by some (many) of the posts. This is one of the best.

> In addition: I experienced significant corruption. I had only
> about 3 files on the XFS filesystem, which was then exported
> via nfs. I ran nfs_stress.sh against it, and my files ended up
> corrupt, and the machine locked up. Ideas?

Even better.

(the purpose of this message is not just to give thanks for the
entertainment, but also perhaps to induce second thoughts about
the wisdom of the setup above, but as a rule people who do this
kind of thing tend to think that they know better)

<Prev in Thread] Current Thread [Next in Thread>