From: Gregory Seidman <gsslist+linuxraid@anthropohedron.net>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: endianness of Linux kernel RAID
Date: Wed, 3 Aug 2005 11:36:17 -0400 [thread overview]
Message-ID: <20050803153617.GA31258@anthropohedron.net> (raw)
In-Reply-To: <42F0C117.5020506@steeleye.com>
On Wed, Aug 03, 2005 at 09:05:27AM -0400, Paul Clements wrote:
} Gregory Seidman wrote:
} >It turns out that if one uses the kernel (2.4.x-2.6.x) RAID support (RAID5,
} >anyway, since that's all I've tested), the RAID'd disks cannot be moved to
} >another system with a different endianness. I don't know how hard that
}
} >Unfortunately, I haven't gotten into kernel development and, therefore, do
} >not have the necessary expertise to fix it. Is anyone here interested in
} >this issue?
}
} Version 1 superblock support, which was recently added to the 2.6 kernel
} and mdadm tool, fixes this issue. Metadata is always stored in little
} endian on disk.
Great! A few questions:
1) Does this mean that the fix will be in 2.6.13?
2) Does the version 1 you refer to have to do with pre-2.6 RAID support?
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?
} Paul
--Greg
next prev parent reply other threads:[~2005-08-03 15:36 UTC|newest]
Thread overview: 13+ 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 [this message]
2005-08-03 15:51 ` Paul Clements
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
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=20050803153617.GA31258@anthropohedron.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).