Devang K Mehta
2001-Nov-01 21:17 UTC
ext3 partition still gets mounted as ext2 for me too!
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
So, it looks like the kernel mounts it as ext2 and never tries ext3. So,
my question is: How can I tell the kernel to mount as ext3 instead of
ext2? Is there something I can edit in /linuxrc of the initrd or is
there a boot parameter which I could try?
Just for completeness, the output of tune2fs -l /dev/hda3 is like this:
tune2fs 1.24a (02-Sep-2001)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: d4bd4742-042d-4c1e-a3cc-e25478b8a072
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1137920
Block count: 2273197
Reserved block count: 113659
Free blocks: 1444614
Free inodes: 984911
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16256
Inode blocks per group: 508
Last mount time: Wed Oct 31 17:28:56 2001
Last write time: Wed Oct 31 17:28:56 2001
Mount count: 3
Maximum mount count: 20
Last checked: Wed Oct 31 06:51:20 2001
Check interval: 15552000 (6 months)
Next check after: Mon Apr 29 07:51:20 2002
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0
Thanks in advance for your help.
cheers,
Devang
--
Devang Mehta
Senior Software Engineer
Mastersoft, Inc.
http://www.mspacific.com
1-650-596-8089
Andreas Dilger
2001-Nov-01 22:56 UTC
Re: ext3 partition still gets mounted as ext2 for me too!
On Nov 01, 2001 13:17 -0800, Devang K Mehta wrote:> 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 > > 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 > ext3Note that the kernel (and mount if you don't give it an fs type) will try to mount in /proc/filesystems order.> So, it looks like the kernel mounts it as ext2 and never tries ext3. So, > my question is: How can I tell the kernel to mount as ext3 instead of > ext2? Is there something I can edit in /linuxrc of the initrd or is > there a boot parameter which I could try?Depending on how your initrd is set up, you should just use "mount -t ext3". The other (much safer) alternative is to include ext3 into the kernel and not as a module, which will make the kernel try ext3 first.> Just for completeness, the output of tune2fs -l /dev/hda3 is like this: > Filesystem features: has_journalThanks for including this. At least it shows us that the filesystem really is ext3 capable. Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
Devang K Mehta
2001-Nov-02 19:45 UTC
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 suggestions. Thanks. Devang 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. http://www.mspacific.com 1-650-596-8089
Chris Howells
2001-Nov-05 21:07 UTC
Re: ext3 partition still gets mounted as ext2 for me too!
On Thursday 01 November 2001 21:17, Devang K Mehta wrote:> 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/mountsThat's because there's a bug in the SuSE /sbin/mk_initrd script Go to suse.co.uk, find the support section, search for "ext3", download the new script, stick it in /sbin, chmod +x it, execute it, and root will mount properly as ext3. (Yes -- I experience this problem as I've only just installed SuSE 7.3, and had to work it out as well! :) ) -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org