From: Paul Clements <paul.clements@steeleye.com>
To: gsslist+linuxraid@anthropohedron.net
Cc: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: endianness of Linux kernel RAID
Date: Wed, 03 Aug 2005 11:51:48 -0400 [thread overview]
Message-ID: <42F0E814.2060403@steeleye.com> (raw)
In-Reply-To: <20050803153617.GA31258@anthropohedron.net>
Gregory Seidman wrote:
> 1) Does this mean that the fix will be in 2.6.13?
Yes, version 1 superblock support is in 2.6.13. You need the latest
mdadm as well.
> 2) Does the version 1 you refer to have to do with pre-2.6 RAID support?
No. 2.4 kernels do not understand version 1 superblocks. They only
support 0.90 superblocks (which is what you've got).
> 3) My existing RAID was original set up under 2.4.18 on PPC, but I'm
> running 2.6.11 now and it works fine... for now. If metadata was
> previously stored in host endian, does that mean that my existing RAID
> that was set up on PPC is going to break, or be upgraded, or what?
You'll have to re-create the array using the version 1 superblock
format. The existing 0.90 superblocks will continue to be used until
you've done that.
--
Paul
next prev parent reply other threads:[~2005-08-03 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 12:07 endianness of Linux kernel RAID Gregory Seidman
2005-08-03 13:05 ` Paul Clements
2005-08-03 15:36 ` Gregory Seidman
2005-08-03 15:51 ` Paul Clements [this message]
2005-08-03 18:50 ` Dan Stromberg
2005-08-04 5:14 ` Neil Brown
2005-08-04 6:47 ` Neil Brown
2005-08-04 7:20 ` Daniel Pittman
2005-08-04 11:40 ` Gregory Seidman
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 4:49 Brent Walsh
2005-08-09 4:57 ` Neil Brown
2005-08-11 13:38 ` Brent Walsh
2005-08-18 4:44 ` Neil Brown
2005-08-01 17:42 Gregory Seidman
2005-08-01 18:18 ` Eugene Surovegin
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=42F0E814.2060403@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=gsslist+linuxraid@anthropohedron.net \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.