Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1089733

Summary: --useexisting not described for btrfs --subvol
Product: [Retired] Fedora Documentation Reporter: Gene Czarcinski <gczarcinski>
Component: install-guideAssignee: Petr Bokoc <pbokoc>
Status: CLOSED DUPLICATE QA Contact: Fedora Docs QA <docs-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, zach
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-01 13:56:40 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 2014-04-21 20:06:25 UTC
Description of problem:
In order to reuse an existing subvol (but not the rootfs), --useexisting must be specified on the btrfs subvol command.  This is not specified in the documentation.

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

Comment 1 Gene Czarcinski 2014-04-22 09:40:13 UTC
The installation guide for Fedora 20 (and 19) need to be updated to make them have the same information as in the "master" kickstart document:
http://fedoraproject.org/wiki/Anaconda/Kickstart

Comment 2 Petr Bokoc 2014-09-01 13:56:40 UTC
Hi,

We're going to be rewriting the whole chapter for F21 and updating all options. In the meantime, you can use the Red Hat Enterprise Linux 7 Installation Guide[1] - available Kickstart commands and options are the same as in Fedora, although the document will be missing a few options which were introduced in F20.

I'll close this bug because we're already tracking this issue - and more - in another one.

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html

*** This bug has been marked as a duplicate of bug 1136025 ***