XFS.. HERE I COME!!!!!!! The LUKS partition was indeed the culprit. The
LUKS partition was not accurately representing the size of the underlying
logical volume (when over 2gb) automatically; in order to handle partitions
over 2gb it is necessary to explicitly specify the desired size of the LUKS
partition (size<lv) to the LUKS partition itself (via the LUKS "resize"
command). It seems that mkfs.xfs relies on an accurate LUKS size in order
to work on logical volumes greater than or equal to 2gb. I updated this
info on the LUKS wiki and other forums...
So just to recap.... if you are getting the error:
"mkfs.xfs: libxfs_device_zero write failed: Input/output error"
make sure that you have resized the underlying LUKS partition to the desired
size.
Thanks for the help; much appreciated.
Eric Sandeen-3 wrote:
>
> pgf111000 wrote:
>> Thank you for the quick response. I have posted on a few luks forums to
>> try
>> to delve into this issue a little deeper; if they are aware of a
>> resolution
>> I'll make sure to post it. The interesting thing is that when I
>> mkfs.ext3
>> on luks partitions above 2-3gb all is fine; I wish xfs and luks would
>> play
>> nice.....
>
> mkfs.xfs actually does writes out at the end of the device and verifies
> them; I'm not sure ext3 is doing the same. You may find yourself in
> trouble on ext3 post-mkfs (or you may not...) I seem to recall that xfs
> has shaken out similar problems on other block devices for this reason.
>
> I'd do some simple device-level read/write tests around 2GB just for
> fun, see how it goes.
>
> -Eric
>
>
>
>
--
View this message in context:
http://www.nabble.com/mkfs.xfs%2C-lvm%2C-multi-terrabyte-hardware-array-and-luks-tf3262532.html#a9074554
Sent from the linux-xfs mailing list archive at Nabble.com.
|