Bug 439205

Summary:	emergency mode shows wrong LVM mount state
Product:	[Fedora] Fedora	Reporter:	Francois Cartegnie <bugzilla77>
Component:	util-linux-ng	Assignee:	Karel Zak <kzak>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-28 10:02:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Francois Cartegnie 2008-03-27 15:22:19 UTC

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 10:02:45 UTC

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).