From: pgf111000 <junkmail@petergfrazier.com>
To: linux-xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks
Date: Tue, 20 Feb 2007 12:00:51 -0800 (PST) [thread overview]
Message-ID: <9069238.post@talk.nabble.com> (raw)
In-Reply-To: <45DB4CE1.3040302@sandeen.net>
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.
next prev parent reply other threads:[~2007-02-20 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 18:56 mkfs.xfs, lvm, multi-terrabyte hardware array and luks pgf111000
2007-02-20 19:32 ` Eric Sandeen
2007-02-20 20:00 ` pgf111000 [this message]
2007-02-20 20:58 ` [PATCH] " Eric Sandeen
2007-02-21 2:50 ` pgf111000
2007-02-21 0:32 ` pgf111000
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9069238.post@talk.nabble.com \
--to=junkmail@petergfrazier.com \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox