hi! i've installed knoppix 3.2 and everything works fine... <suspense>... except... i get the following warning in syslog (dmesg):

Code:
EXT2-fs warning (device ide0(3,5)): ext2_read_super: mounting ext3 filesystem as ext2
when i installed knoppix i specified the root partition (/dev/hda5) to use ext3 as filesystem and then afterward added and mounted my existing '/home/' partition (/dev/hda6) as ext3. firstly, here are the relevant parts of my /etc/fstab:

Code:
...
/dev/hda5  /          ext3  defaults,errors=remount-ro  0  1
/dev/hda6  /home  ext3  defaults                               0  1
...
the output from 'mount':

Code:
# mount
/dev/hda5 on / type ext3 (rw,errors=remount-ro)
none on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda6 on /home type ext3 (rw)
BUT! look at this... the output of 'cat /proc/mounts':


Code:
# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda6 /home ext3 rw 0 0
it looks like there seems to be only one instance of kjournald running (for my /home/ partition i assume)

Code:
# ps aux| grep kjournald
root       137  0.0  0.0     0    0 ?        SW   18:27   0:00 [kjournald]
root      1670  0.0  0.0  1288  424 pts/0    R    21:29   0:00 grep kjournald
when i have the occasional crash, fsck is run on /dev/hda5, but never on /dev/hda6. yet both are supposed to be journaling. i have had corruption on my root partition as a result.

i've done some searching on google and groups.google (see second item below 'old stuff' http://groups.google.co.nz/groups?hl...1%40zip.com.au) and it seems that the problem is that the kernel is loaded, but it can't access the root partition using ext3, because it doesn't have ext3 support compiled in - as ext3 is compiled as a module. so instead it mounts it as ext2. so i could presumably compile a kernel with ext3 built in and run lilo. call me picky, but i really think that if knoppix allows you to format a root partition as ext3, it should mount it as ext3 in the future...

the other alternative is something to do with the way initrd works, but i'm completely lost when it comes to that.

what should i do?

sorry for the long post. i wanted to make sure i supplied all the info i could.

cheers
julian