Bug 1011137

Summary: RFE: add capability to re-use btrfs subvolume
Product: [Fedora] Fedora Reporter: Gene Czarcinski <gczarcinski>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, samuel-rhbugs, sbueno, vanmeeuwen+fedora
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: 2015-03-13 14:21:46 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:
Embargoed:

Description Gene Czarcinski 2013-09-23 16:30:46 UTC
Description of problem:
If you install on a regular partition of an LVM logical-volume, you can can reuse an  existing definition and simply reformat it.  This does not work for btrfs because reformatting a btrfs subvolume really has no meaning but having the same functionality would be useful.  Therefore, this is an RFE to implement that.

Specifically, the request is to add some new kickstart parameter such as "--reuse" which will result in the specified (named) subvolume being deleted and then reallocated.  The primary use for this will be for root ("/").

I am specifying "rawhide" rather than a specific release since this should continue until satisfied.

Comment 1 Gene Czarcinski 2014-07-21 16:48:42 UTC
Still true as of this date.  I have a pair of patches for pykickstart and anaconda which adds the "--reclaim" option for a btrfs --subvol so that, if a named subvol exists, it will be deleted before being re-allocated.  The patches have been submitted to anaconda-patches.

Comment 2 David Lehman 2015-03-13 14:21:46 UTC
There have been numerous exhaustive discussions on mailing lists about why this is not necessary or acceptable from the maintainer's POV.