On 30.11.05 11:15:12, Bart Samwel wrote:
> Andreas Pakulat wrote:
> >since the last upgrade of laptop-mode-tools (to version 1.11-1)
> >laptop-mode-tools always issues a "BIG FAT WARNING" during boot and when
> >I restart it manually.
> >The problem seems to be that it cannot remount "/" setting another
> >commit-timeout. Now my Kernel has ext3 support built into it, it mounts
> >"/" as ext3 and I do not see any option indicating a specific kernel
> >option to disable the commit Option.
> >I have other ext3 partitions that don't seem to issue any warning.
> 
> Hmmm, if it issues this warning then your root filesystem probably *isn't* 
> mounted as ext3 for some reason.

I guess I should have put some evidence into the report, now here it
comes:

[EMAIL PROTECTED]:~>mount | grep "hda2"
/dev/hda2 on / type ext3 (rw,errors=remount-ro)
[EMAIL PROTECTED]:/boot>uname -r
2.6.14-cherry+radeon+ipw2100+ieee80211
[EMAIL PROTECTED]:/boot>grep EXT3 config-2.6.14-cherry+radeon+ipw2100+ieee80211
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set

> You say that your kernel has ext3 support built-in, but are you sure ext3 is 
> not built as a module?

see above.

> Could you do the following:
> 1. Show me the entries for your root fs in /proc/mounts, /etc/mtab and 
> /etc/fstab?

[EMAIL PROTECTED]:~>cat /etc/mtab
/dev/hda2 / ext3 rw,errors=remount-ro 0 0
[EMAIL PROTECTED]:~>cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext2 rw,nogrpid 0 0

Is this right? The output of proc mounts seems a bit "strange" to me...

> 2. Do a "mount / -o remount,commit=600" and show me the output.
 
[EMAIL PROTECTED]:~>mount / -o remount,commit=600
mount: / not mounted already, or bad option

Hmm, now it gets interesting...  Aaah, Ok found this in the kern.log:
Nov 29 23:11:51 morpheus kernel: fill_kobj_path: path = '/block/hda/hda2'
Nov 29 23:11:51 morpheus last message repeated 2 times
Nov 29 23:11:51 morpheus kernel: VFS: Mounted root (ext2 filesystem) readonly.

Why the hell is it mounted as ext2, when it really is ext3? I recently
removed the journal via tune2fs -O ^has_journal /dev/hda2 and later I
added it again using tune2fs -O has_journal /dev/hda2. Maybe that got
something to do with it... Do you have any idea? If not please close
this bug report as invalid and I'll try to find some help und
debian-user-german.

Andreas

-- 
Keep emotionally active.  Cater to your favorite neurosis.

Attachment: pgpRJJ5Cmh7RR.pgp
Description: PGP signature

Reply via email to