You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
blivet-gui fails to display a VG under the LVM header in the sidebar when one of the PVs of the VG is missing. I had a drive die on me (a cache disk). The LVM started working again after I lvremoved the cache pool, but it still didn’t show up in blivet-gui. It only reappeared there after I removed the PV from the VG.
bliviet-gui should still display a troubled LVM and identify the problem; and ideally even let users fix the problem.
Steps to reproduce: Setup a VG consisting of two PVs. Add a LV on one of the PVs and setup the other PV as a cache for the LV on the first PV. Then remove the PV with the cache.
The text was updated successfully, but these errors were encountered:
Unfortunately blivet by default ignores incomplete VGs and there is no way how to tell it to not do that. This would require quite a big changes in blivet, but I agree it would be nice to have a way how to fix this (missing pvs) from blivet-gui.
See rhinstaller/anaconda#1377, which is sort of along the same lines. I'm pretty open to changing this behavior in blivet. It would take some extra work for LVM though, since we'd potentially have some usable LVs and some non-usable LVs when there are missing PVs.
blivet-gui fails to display a VG under the LVM header in the sidebar when one of the PVs of the VG is missing. I had a drive die on me (a cache disk). The LVM started working again after I lvremoved the cache pool, but it still didn’t show up in blivet-gui. It only reappeared there after I removed the PV from the VG.
bliviet-gui should still display a troubled LVM and identify the problem; and ideally even let users fix the problem.
Steps to reproduce: Setup a VG consisting of two PVs. Add a LV on one of the PVs and setup the other PV as a cache for the LV on the first PV. Then remove the PV with the cache.
The text was updated successfully, but these errors were encountered: