|
Bugzilla – Full Text Bug Listing |
| Summary: | mount displays different info then is in /proc/mounts | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Ladislav Michnovic <lmichnovic> |
| Component: | Kernel | Assignee: | Mads Martin Joergensen <mmj> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | asklein, jason_mack, suse-beta, vetter, werner, wwlinuxengineering |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ladislav Michnovic
2006-01-27 16:24:42 UTC
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 |