3:04 a.m.
I've tried a couple of kernels post 2.6.8-1.533 and they all die on
switching to the new root as a pile of journal_ symbols are missing
from the ext3 module.
Just me, or are others seeing this?
--
Alex Kiernan
12:41 a.m.
On Tue, 7 Sep 2004 09:04:55 +0100, Alex Kiernan <alex.kiernan(a)gmail.com> wrote:
I've tried a couple of kernels post 2.6.8-1.533 and they all die
on
switching to the new root as a pile of journal_ symbols are missing
from the ext3 module.
Just me, or are others seeing this?
--
Alex Kiernan
I'm seeing the same on Fedora x86, actually.
--
Michel Salim ζζΊε
http://salimma.livejournal.com
7:07 a.m.
On Tue, 2004-09-07 at 18:04, Alex Kiernan wrote:
I've tried a couple of kernels post 2.6.8-1.533 and they all die
on
switching to the new root as a pile of journal_ symbols are missing
from the ext3 module.
.540 should be fine, x86 users have .541 issues
Just me, or are others seeing this?
My iMac DV is running .541, and I'm happy to report, it all seems to
"just work". Weird, especially with heaps complaining on
fedora-test-list(a)redhat.com
It could be before .538 as the last good known working kernel for
many... ext3 online resizing among others might be causing issues (I
have a feeling no one really knows for sure, at this stage)
--
Colin Charles, byte(a)aeon.com.my
http://www.bytebot.net/
"First they ignore you, then they laugh at you, then they fight you,
then you win." -- Mohandas Gandhi
7:17 a.m.
On Wed, 2004-09-08 at 22:07 +1000, Colin Charles wrote:
On Tue, 2004-09-07 at 18:04, Alex Kiernan wrote:
> I've tried a couple of kernels post 2.6.8-1.533 and they all die on
> switching to the new root as a pile of journal_ symbols are missing
> from the ext3 module.
.540 should be fine, x86 users have .541 issues
> Just me, or are others seeing this?
My iMac DV is running .541, and I'm happy to report, it all seems to
"just work". Weird, especially with heaps complaining on
fedora-test-list(a)redhat.com
I'm runnig .538, and I have run .541 but reverted due to the scary
reports of ext3 corruption. I suspect the problem is with
module-init-tools -- I was seeing modprobe segfault at one point
recently, and if mkinitrd is using modprobe to list the dependencies of
the ext3.ko module then we could miss jbd.ko out of the initrd.
Rebuild your initrd and check it contains jbd.ko. If not, try an older
(or newer) module-init-tools.
We _really_ ought to be shipping kernels with ext3 support built in.
Shipping it as a module is just gratuitously fragile.
--
dwmw2
8:22 a.m.
On Wed, 08 Sep 2004 13:17:36 +0100, David Woodhouse <dwmw2(a)infradead.org> wrote:
On Wed, 2004-09-08 at 22:07 +1000, Colin Charles wrote:
> On Tue, 2004-09-07 at 18:04, Alex Kiernan wrote:
> > I've tried a couple of kernels post 2.6.8-1.533 and they all die on
> > switching to the new root as a pile of journal_ symbols are missing
> > from the ext3 module.
>
> .540 should be fine, x86 users have .541 issues
>
> > Just me, or are others seeing this?
>
> My iMac DV is running .541, and I'm happy to report, it all seems to
> "just work". Weird, especially with heaps complaining on
> fedora-test-list(a)redhat.com
I'm runnig .538, and I have run .541 but reverted due to the scary
reports of ext3 corruption. I suspect the problem is with
module-init-tools -- I was seeing modprobe segfault at one point
recently, and if mkinitrd is using modprobe to list the dependencies of
the ext3.ko module then we could miss jbd.ko out of the initrd.
Rebuild your initrd and check it contains jbd.ko. If not, try an older
(or newer) module-init-tools.
Yup, thats it - jbd.ko isn't getting included. Do a --preload on it at
mkinitrd time & it all works.
--
Alex Kiernan
7169
days inactive
7170
days old
4 comments
4 participants
participants (4)
-
Alex Kiernan -
Colin Charles -
David Woodhouse -
Michel Salim