Bug 439205 - emergency mode shows wrong LVM mount state
emergency mode shows wrong LVM mount state
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: util-linux-ng (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Karel Zak
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-27 11:22 EDT by Francois Cartegnie
Modified: 2008-04-28 06:02 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-28 06:02:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Francois Cartegnie 2008-03-27 11:22:19 EDT
Description of problem:
When booted in emergency runlevel, the LVM partitions are mounted, but mount
shows incorrect mount state as RW.
So, you can't also use any of lvm-tools at they try to lock into /var/lock/lvm,
which is not writable.

Version-Release number of selected component (if applicable):
2.13-3.fc8

How reproducible:
boot in emergency mode runlevel with LVM arrays

Actual results:
mount shows incorrect RW for LVM arrays, while it is mounted RO
You can only manipulate lvm arrays with lvm tools by remounting rw
mount / -o remount,rw

Additional info:
Comment 1 Karel Zak 2008-04-28 06:02:45 EDT
mount(8) reads /etc/mtab, when the root partition is read-only this file can't
be updated to fit reality. In particular case, mount(8) output is useless...

I don't see a simple way how to fix this problem. I hope we will remove the mtab
file from Linux one day (but it's long-term task).

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