I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules. /etc/mtab reports the filesystem mounted ext3 /proc/mounts reports it mounted ext2 /proc/filesystems lists ext3 If I umount other partitions that are ext3 the module becomes 'unused'. The filesystem was created 'properly' with mke2fs -j, and mounts as ext3 if it is compiled in the kernel. Question is: Am I doing something wrong, or is this a bug? (The initrd boot procedure works with reiserfs) Thanks, Andreas
On Sat, Nov 10, 2001 at 04:56:16PM -0500, Andreas Boman wrote:> I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules. > > /etc/mtab reports the filesystem mounted ext3 > /proc/mounts reports it mounted ext2 > /proc/filesystems lists ext3 >But in what order is ext2 and ext3 in /proc/filesystems? Is ext3 first? Really, this question has been asked so many times in the last couple months, it's ridiculous. Mike
Pardon my ignorance, but if your root filesystem is ext3, why would you not want ext3 compiled directly into the kernel? I mean, there's no circumstance in which you're going to want ext3 support unloaded; you're not gonna umount your root filesystem, right? Or am I missing something?
Hi, On Sat, Nov 10, 2001 at 04:56:16PM -0500, Andreas Boman wrote:> I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules.> /etc/mtab reports the filesystem mounted ext3 > /proc/mounts reports it mounted ext2 > /proc/filesystems lists ext3 > > If I umount other partitions that are ext3 the module becomes 'unused'. > The filesystem was created 'properly' with mke2fs -j, and mounts as ext3 if it is compiled in the kernel. > > Question is: Am I doing something wrong, or is this a bug?Your initrd needs to specify the filesystem type when it mounts the root filesystem. At least on Red Hat systems, that is done by making sure that /etc/fstab has the right fstype in place when you create your initrd with mkinitrd. Rerunning mkinitrd (and then lilo if you're not using grub) ought to fix things if this is all that's wrong. Cheers, Stephen