[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimRDH4S1QMN6f4AfKOe6ipPK6jm+g91nuBJYQJa@mail.gmail.com>
Date: Tue, 15 Mar 2011 08:10:31 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Michael Cree <mcree@...on.net.nz>
Cc: linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org,
warns@...-sense.de
Subject: Re: Alpha no longer recognises certain partition tables (v2.6.38)
On Tue, Mar 15, 2011 at 2:06 AM, Michael Cree <mcree@...on.net.nz> wrote:
> v2.6.38 boot reports it can't recognise the partition table on the system
> disk on my Alpha and panics when it can't find the root device.
>
> It worked at v2.6.38-rc7.
>
> While I haven't done a bisect to fully verify I nevertheless suggest the
> following patch as the likely cause:
>
> 1eafbfe Fix corrupted OSF partition table parsing
That sounds likely. What does something like the attached do? In
particular, what's the printed-out value of the OSF npartitions thing?
Also, it's quite possible that we should raise the value of
MAX_OSF_PARTITIONS. If I checked it right, the d_partitions[] array
starts at byte offset 148 in the sector, and it's 16 bytes in size, so
there _could_ be up to 22 partitions there. The fact that we had
defined the 'struct disklabel' to only contain 8 partitions is I think
from documentation, not a technical "there can be only eight".
Linus
View attachment "patch.diff" of type "text/x-patch" (595 bytes)
Powered by blists - more mailing lists