http://qa.mandrakesoft.com/show_bug.cgi?id=3561
Product: kernel
Component: libsasl2-plug-ntlm
Summary: kernel mounts / as ext2 instead of ext3 in mandrake-9.1
Version: 2.4.21-0.13mdk
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
My root partition (/ on /dev/hda5) is an ext3 partition but at boot, the kernel always
mounts it
as ext2. This problem was not there in mandrake-9.0 kernels.
1. /etc/fstab has the correct options for mounting it as ext3
/dev/hda5 / ext3 noatime,defaults 1 2
So "df -T /dev/hda5" reports it as ext3 too:
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda5 ext3 3.4G 713M 2.5G 22% /
2. But "dmesg" shows these entries:
VFS: Mounted root (ext2 filesystem).
EXT2-fs warning (device ide0(3,5)): ext2_read_super: mounting ext3 filesystem as ext2
Similarly, "cat /proc/mounts" shows:
/dev/root / ext2 rw,noatime 0 0
These mean / is being mounted as ext2, not ext3.
This is further confirmed by the lsmod entry:
Module Size Used by Not tainted
ext3 64704 3 (autoclean)
which shows that 3 other ext3 partitions are mounted as ext3 as expected. If / had
been
mounted as ext3, the "Used by" field would have been 4.
Its obvious that the kernel (which has ext2 built-in but modular ext3 support) is
preferring ext2
to ext3. This is inspite of the fact that my installation has initrd:
lrwxrwxrwx 1 root root 25 Mar 26 19:44 /boot/initrd.img ->
initrd-2.4.21-0.13mdk.img
and /etc/lilo.conf has the correct entry for initrd:
image=/boot/vmlinuz
label="linux"
root=/dev/hda5
initrd=/boot/initrd.img
Something must be wrong with the way initrd-2.4.21-0.13mdk.img has been built and that
is
preventing the kernel from loading / as ext3.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
