Do a google on '/dev2/root2' and you will see that /proc/mounts on Debian reports false information for the root filesystem device, and this is a longstanding problem. The result is that on systems with this problem /etc/mtab is correct but /proc/mounts is not.
This appears to be more a kernel problem than a distribution problem - how is it even _possible_ for some userspace process to get /proc/mounts to publish erroneous information? Why are there no consistency checks in /proc/mounts?
$ cat /proc/mounts
rootfs / rootfs rw 0 0
/dev2/root2 / ext3 rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
/dev/hda1 /boot ext2 rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
$ ls -l /dev2 /dev2/root2
ls: /dev2: No such file or directory
ls: /dev2/root2: No such file or directory
$ mount -l
/dev/hda2 on / type ext3 (rw,errors=remount-ro) [debian-sarge-roo]
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda1 on /boot type ext2 (rw) [/boot]
usbfs on /proc/bus/usb type usbfs (rw)
$ uname -a
Linux nectarsys 2.6.10-1-k7 #1 Fri Mar 11 03:13:32 EST 2005 i686 GNU/Linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]