xfs
[Top] [All Lists]

Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks

To: linux-xfs@xxxxxxxxxxx
Subject: Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks
From: pgf111000 <junkmail@xxxxxxxxxxxxxxxxx>
Date: Tue, 20 Feb 2007 12:00:51 -0800 (PST)
In-reply-to: <45DB4CE1.3040302@xxxxxxxxxxx>
References: <9068053.post@xxxxxxxxxxxxxxx> <45DB4CE1.3040302@xxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
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.....


Eric Sandeen-3 wrote:
> 
> pgf111000 wrote:
>> When I try to format partitions above 2-3gb my opteron experiences heavy
>> io
>> wait; the mkfs.xfs fails, and I receive the following....
>> 
>>  "mkfs.xfs: libxfs_device_zero write failed: Input/output error"
>> 
>> When I format partions below 2-3gb, there is no problem whatsoever.  I
>> can
>> mkfs.xfs on a +2-3GB non-luks formated partition without a problem... any
>> thoughts?
> 
> Sounds like a LUKS problem, maybe it can't do those large offsets?  xfs
> certainly can...
> 
> I bet you'll find that the 2GB size is the threshold... xfs is just
> trying a write():
> 
>         if ((bytes = write(fd, z, bytes)) < 0) {
>                 fprintf(stderr, _("%s: %s write failed: %s\n"),
>                         progname, __FUNCTION__, strerror(errno));
> 
> maybe try a simple dd write at the end of your large luks device, see
> how that goes.
> 
> -Eric
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/mkfs.xfs%2C-lvm%2C-multi-terrabyte-hardware-array-and-luks-tf3262532.html#a9069238
Sent from the linux-xfs mailing list archive at Nabble.com.


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