You probably grabbed CVS at exactly the wrong time; there was a bug
introduced and fixed this morning that prevented booting if there were no
command-line parameters to the kernel and the root fs is XFS. Try updating
from CVS again and building a new kernel.
Jesse
----- Original Message -----
From: "Wm. Josiah Erikson" <josiah@xxxxxxxxxxxxxxxxxxxx>
To: <linux-xfs@xxxxxxxxxxx>
Sent: Tuesday, December 18, 2001 1:21 PM
Subject: Question about 2.4.16
> Hey all,
> I just got myself a new tape drive and went to recompile my kernel
> with support for it, and figured that I might as well get myself the
> latest kernel source tree to do it with, so I did a CVS update and got
> 2.4.16. I had been using 2.4.13-pre6, which has been working fine. With
> 2.4.16, I get this message on bootup, as it tries to mount the root fs:
>
> XFS: invalid logbufsize
>
> And then it kernel panics (unable to mount root filesystem).
>
> Did something change, or am I stupid? My fstab looks like this:
>
> /dev/sda1 / xfs defaults 1 1
> /dev/md0 /home xfs defaults 1 2
> /dev/sda2 none swap sw,pri=1 0 0
> /dev/hda1 none swap sw,pri=1 0 0
> /dev/hdc1 none swap sw,pri=1 0 0
> /dev/hde1 none swap sw,pri=1 0 0
> /dev/hdg1 none swap sw,pri=1 0 0
> proc /proc proc defaults 0 0
>
> And my lilo.conf looks like this:
>
>
> lba32
>
> boot=/dev/hda
> install=/boot/boot.b
> map=/boot/map
> prompt
> timeout=30
> delay=20
> vga=extended
>
> default=Linux
>
> image=/vmlinuz
> label=Linux
> read-only
> root=/dev/sda1
>
> image=/vmlinuz.old
> label=LinuxOLD
> read-only
> optional
> root=/dev/sda1
>
>
>
> Booting up with 2.4.13-pre6 still works fine, but I lost that kernel
> source tree when I updated, so I can't build tape support in :)
>
> If anybody has any clues, that would be great. Let me know if you need any
> more info.
> Thanks!
> -Josiah
>
>
|