[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 partition still gets mounted as ext2 for me too!

I am not the biggest expert on initrd's. What I know is from the SuSE
documentation and their linuxrc doesn't actually mount the root
filesystem. It writes something to the proc filesystem and exits and
then leaves it to the kernel to do the right thing. The kernel then
figures out which driver to use and it seems to pick the ext2 driver
because it is higher up on its list.

SuSE probably wanted to keep the kernel minimal and wanted the drivers
to come up through initrd and so they only kept ext2 in the kernel. In
case of JFS or other filesystems, it doesn't really matter since there
is no confusion and that's probably why they didn't anticipate this
situation. I am cc'ing this message to the suse-linux-e suse com mailing
list so that someone will see this message and hopefully there will be
an update. It is a bit inconvenient to recompile the kernel for every
machine that needs to have an ext3 root filesystem :-)

Anyway, I recompiled the kernel with both ext2 and ext3 drivers  and
everything is working fine. Thanks to you and Andreas for your


mb/ext3 dcs qmul ac uk wrote:
> Is it possible that with ext2 compiled in (which you are probably needing
> for your initrd) and ext3 as modules, your / will be mounted ext2?
> I have no such problems and I have both ext2 and ext3 built as modules; my
> initrds use romfs and I can choose which filesystem to use for / by using
> different initrds :)
> Cheers,
> Matt
> On Nov 1 Devang K Mehta wrote:
> >Hi,
> >
> >I am a new ext3 user and I am having problems similar to what many
> >people are facing on this list.
> >
> >I have done everything as the emails suggest. I am using SuSE 7.3 with
> >the the 2.4.10 kernel and ext3 compiled as a module. Because it is
> >2.4.10 kernel, I created all my journals from a rescue disk and
> >everything seems to be working right for the non-root filesystems. My
> >fstab has all my filesystems showing as ext3 and mtab reflects that. In
> >order to make the ext3 module available to the initrd image I added the
> >ext3 and jbd modules. The bootup messages confirm that these modules are
> >being loaded. Even after doing all that, my root filesystem still gets
> >mounted as ext2. Here is the output of /proc/mounts
> >
> >/dev/root / ext2 rw 0 0
> >proc /proc proc rw 0 0
> >devpts /dev/pts devpts rw 0 0
> >/dev/hda1 /boot ext3 rw 0 0
> >/dev/hdb1 /data ext3 rw 0 0
> >shmfs /dev/shm shm rw 0 0
> >usbdevfs /proc/bus/usb usbdevfs rw 0 0
> >cuda:/lmaster/home /master nfs
> >rw,v3,rsize=8192,wsize=8192,soft,udp,lock,addr=cuda 0 0
> >mako:/ldist /ldist nfs
> >rw,v3,rsize=32768,wsize=32768,soft,udp,lock,addr=mako 0 0mako:/software
> >/software nfs rw,v3,rsize=32768,wsize=32768,soft,udp,lock,addr=mako 0 0
> >
> >
> >The output of /proc/filesystems is like this:
> >
> >nodev   bdev
> >nodev   proc
> >nodev   sockfs
> >nodev   tmpfs
> >nodev   shm
> >nodev   pipefs
> >        ext2
> >        minix
> >        msdos
> >        vfat
> >        iso9660
> >nodev   nfs
> >nodev   devpts
> >nodev   usbdevfs
> >        ext3

Devang Mehta
Senior Software Engineer
Mastersoft, Inc.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]