Bug 125706
Summary: | can't make root volume read-write again | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | 157070.alewis |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-06-10 14:35:36 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
Alexandre Oliva
2004-06-10 13:39:44 UTC
The logical volume can't change from read-write to read-only on its own as far as I know. lvchange -p needs to write metadata so there's no way it can be allowed to ignore locking failures. It's a requirement of using the tools that you have a rw lock directory e.g. tmpfs. The locking directory shouldn't really ever be on an LV, of course. Ok, so maybe mount -o remount,rw / simply refused to mount the root filesystem because it contained errors (which is likely, since the machine didn't come back up). Bug report withdrawn, but feel free to leave it open if you'd like a reason to work on keeping the metadata in tmpfs or so. The point about how to recover from setting the only LV which also contains the locking to read-only ought to go into the FAQ. |