Bug 1023426

Summary: Reclaim space: not enough information to reclaim what is intended to be reclaimed
Product: [Fedora] Fedora Reporter: Marian Csontos <mcsontos>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-13 17:03:05 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:

Description Marian Csontos 2013-10-25 11:40:23 UTC
Description of problem:
Reclaim space displays only VG names which is not enough to make qualified guess which PV should be removed.

What's worse it does not display VG name when PV is directly on disk (without partition) so one can not distinguish free PV from allocated PV.

Neither is VG name displayed when not all disks in a VG were selected in "Installation destination" (Bug 1022811).

It also allows reclaiming single PV from a VG without warning user (similar to Bug 1022811.)

Version-Release number of selected component (if applicable):

How reproducible:


1. PV (whether used or unused by VG) directly on disk without partition - lvmpv only, no VG name to indicate it is in use
- When VG is used the name MUST be displayed.

2. VG - vg name + lvmpv is displayed. No information about LVs.
- When VG contains LVs there MUST be a way to display those.

3. Partial VG on a partition selected - lvmpv only is displayed (may look like unused PV)
- This should be prevented by resolving Bug 1022811.

4. Allows user to remove single PV from VG with multiple PVs wihthout warning.
- User MUST be warned given a chance to review affected LVs and decide what to do (keep PV, delete whole VG or force-delete single PV with emphasized disclaimer.)

5. Impossible to remove existing LVs (and pools).
- User SHOULD be able to remove existing LVs.

Comment 1 David Shea 2015-04-13 17:03:05 UTC
1) both the VG name and the name of the partition containing the lvmpv are displayed

2) Removing a partition from a volume group will effectively destroy the VG, and LVs to PVs is a potentially many to many relationship. Displaying LV information in the reclaim dialog is neither feasible nor useful.

3+4) bug 1209223

5) This is not the level the reclaim space dialog works at, use custom partitioning.

Comment 2 David Shea 2015-04-13 17:08:34 UTC
*** Bug 1023459 has been marked as a duplicate of this bug. ***