[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Couple more fixes for Linux raid metadata 1.x support
From: |
Lennart Sorensen |
Subject: |
Re: Couple more fixes for Linux raid metadata 1.x support |
Date: |
Mon, 26 Jul 2010 13:20:34 -0400 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Sat, Jul 24, 2010 at 06:22:02AM -0400, Doug Nazar wrote:
> While doing some in-depth testing came across a few more issues. The
> second one really threw me for a loop. The LVM wouldn't come up because
> it couldn't find some of the raid arrays but when I hexdumped the raid
> arrays it showed the correct uuid. Applies on top of previous patch.
>
> - Ignore spare and faulty drives
> - Set a dynamic array->number. It's used for the disk->id and is important
> for the cache subsystem that it be unique.
I just tried this patch with a fresh checkout. I still can't get grub
to read my 1.x raids (That I just created using the debian installer
daily build).
If I use 0.9 raid, it seems to work fine.
I keep getting errors like:
Welcome to GRUB!
error: read error on block: 18446744073709551360.
error: no such disk.
Entering rescue mode...
grub rescue>
Now this is on a powerpc64 system, so it is big endian. That number by
the way is FFFFFFFFFFFFFF00.
I wonder if some part of the 1.x raid handling code has an endianess bug.
Got any guesses I can try before I just go convert back to 0.9 raids?
I really hate giving up on things that ought to work and loose the
debugging opportunity.
--
Len Sorensen