From: Eric Sandeen <sandeen@sandeen.net>
To: "Jochen K." <jochen.f.k@googlemail.com>
Cc: nscott@aconex.com, xfs@oss.sgi.com
Subject: Re: Cant find sunit and swidth on luks encrypted raid6 device
Date: Wed, 19 Sep 2007 17:56:54 -0500 [thread overview]
Message-ID: <46F1A936.8060706@sandeen.net> (raw)
In-Reply-To: <728b8e3b0709191550q3adad31bx53e759f66808d8b@mail.gmail.com>
Jochen K. wrote:
> Hi, Eric
>
> Here is the output you wanted. I also did some debuging with strace but
> its kinda big to paste it in here.
> I also tried with the size option using a smaller device size which was
> working but still using wrong optimized values for the raid6 device.
> I guess you found the bug up there so should I add that and recompile
> xfsprogs to try again ?
Let's let Barry chime in.
I got off on a luks thing, saw "key lookup" and thought it was unique to
luks. Didn't realize that message came from libxfs :) Oh well...
Also FWIW, the issue w/ sunit/swidth is unrelated to the error message.
It has more to do with xfs not knowing how to get that geometry out of
the encrypted block device (and hmmm is it even relevant in that case?
As long as it just encrypts each individual block, I suppose it still is
relevant).
-Eric
next prev parent reply other threads:[~2007-09-19 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 18:29 Cant find sunit and swidth on luks encrypted raid6 device Jochen K.
2007-09-19 19:40 ` Bhagi rathi
2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33 ` Eric Sandeen
2007-09-19 22:39 ` nscott
2007-09-19 22:47 ` Eric Sandeen
2007-09-19 22:50 ` Jochen K.
2007-09-19 22:56 ` Eric Sandeen [this message]
2007-09-20 0:54 ` Barry Naujok
2007-09-20 2:36 ` Barry Naujok
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=46F1A936.8060706@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jochen.f.k@googlemail.com \
--cc=nscott@aconex.com \
--cc=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