Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 56470 - mount fs bad report
mount fs bad report
Product: Red Hat Linux
Classification: Retired
Component: mount (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2001-11-19 11:11 EST by acount closed by user
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-19 11:11:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description acount closed by user 2001-11-19 11:11:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
when I go to single mode from grub , then I remount / (ro) . mount report
(rw) but the output from /pro/mount  is (ro)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. single mode
2. mount -o  ro,remount /
3. mount ; cat /proc/mount

Additional info:
Comment 1 Bernhard Rosenkraenzer 2001-11-20 10:25:30 EST
This is expectable:
mount shows the content of /etc/mtab.
If /etc isn't writable, /etc/mtab can't be updated, therefore mount will 
display outdated content.

See the mount man page for details, including why having mount read 
/proc/mounts rather than /etc/mtab is not necessarily a good idea.
Comment 2 acount closed by user 2001-11-20 16:11:40 EST
I think that /etc/mtab must be deleted every reboot at /etc/rc.d/init.d/halt
because when you are booting with root fs (/) in ro /etc/mtab must be empty
because _anything_ can write this file and it false the content.

well this example was not true:
1. single mode
2. mount -o  ro,remount /
3. mount ; cat /proc/mount

but if you are booting _emergency_ mode or with external media like a cdrom or
fd is true
Comment 3 acount closed by user 2001-11-20 16:22:14 EST
"because _anything_ can write this file and it false the content."

change _anything_ for  "none process"

i am sorry, english is my third language

Note You need to log in before you can comment on or make changes to this bug.