Bug 1024714
Summary: | mount displays FS as read-write (rw) but the FS is read-only (ro) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nenad Peric <nperic> |
Component: | util-linux-ng | Assignee: | Karel Zak <kzak> |
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-31 12:46:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nenad Peric
2013-10-30 10:00:30 UTC
> mount: warning: /etc/mtab is not writable (e.g. read-only filesystem). > It's possible that information reported by mount(8) is not > up to date. For actual information about system mount points > check the /proc/mounts file. I guess this warning explains everything. It's known issue. > Expected results: > If a FS is read-only, mount command should not tell the user that it is > read-write. It means that mount(8) has to re-verify all information from /etc/mtab. It's ugly task and invasive change to mount(8) code. Sorry, won't fix. Note that this problem does not exist on RHEL7/Fedora where we don't use /etc/mtab any more. Well I can understand a reluctance to fix a known issue.. I suppose if it is too complicated and dangerous, it makes sense. Could the output just be modified, since 'mount' obviously knows it has issues sometimes. Say, to put in those brackets (unknown) or nothing at all since the information such as (rw) is quite unreliable? And even leaving the warning below as a complementary hint of what to do next is quite good. That should not be such an invasive and destructive change, it is just a matter of changing some of the output but would make it probably clearer to the user that mount actually has no clear idea of what is going on at that time. Saying (rw) when in fact it is not really known, is misleading :) |