Bugzilla – Bug 146192
mount displays different info then is in /proc/mounts
Last modified: 2006-02-06 16:36:55 UTC
As root or user I when I type mount, the output is mount /dev/sda1 on / type reiserfs (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) cat /proc/mounts rootfs / rootfs rw 0 0 udev /dev tmpfs rw 0 0 /dev/sda1 / reiserfs rw 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw 0 0 /dev/sda5 /home ext2 rw,nogrpid 0 0 The last line is not displayed but it is mounted.
mount reads /etc/mtab, /proc/mounts is maintained by the kernel. mmj?
Actually, in /etc/mtab I don't see any line with my home, /dev/sda5. But it is mounted by default during boot. Evyrething works, but only I just can't see it in output of mount.
Maybe this bug is related to bug #146047
*** Bug 146047 has been marked as a duplicate of this bug. ***
Whereas df only reads /etc/mtab and does its job, the mount program also writes /etc/mtab. Maybe there is a bug in mount its selfs or the behaviour is caused by an `-n' option in one of the boot scripts (-n for not updateing /etc/mtab).
I think there is something wrong with system startup scripts: Checking file systems... fsck 1.38 (30-Jun-2005) /dev/hda2 is mounted. e2fsck: Cannot continue, aborting. fsck.ext2 /dev/hda2 failed (status 0x8). Run manually! /dev/hda6 is mounted. e2fsck: Cannot continue, aborting. fsck.ext3 /dev/hda6 failed (status 0x8). Run manually! doneSetting up kernel module dependencies (if required)done Mounting local file systems... proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) mount: /dev/hda2 already mounted or /boot busy mount: /dev/hda6 already mounted or /home busy
*** Bug 146055 has been marked as a duplicate of this bug. ***
I had also this problem in beta2. Beta3 does not show the problem on my machine, so it seems to be fixed.
i consider this fixed in beta3. please reopen if not