Bug 1008212

Summary:	OS Installer Support for LVM Thin Provisioning
Product:	[Fedora] Fedora Documentation	Reporter:	Pete Travis <me>
Component:	storage-administration-guide	Assignee:	Ruediger Landmann <rlandman>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	dlehman, jreznik, nobody, stickster, zach
Target Milestone:	---	Keywords:	Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	998527	Environment:
Last Closed:	2019-11-07 15:30:00 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:
Bug Depends On:	998527, 1021570
Bug Blocks:	998532

Description Pete Travis 2013-09-15 18:54:58 UTC

+++ This bug was initially created as a clone of Bug #998527 +++

This is a tracking bug for Change: OS Installer Support for LVM Thin Provisioning
For more details, see: http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport

LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation.

--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---

The only missing piece is a way to select a usage profile in anaconda. You specify metadata size and chunk size via kickstart. The bug to add profiles to lvm2 for common thinp usage patterns is bug 958464.

--------------------------------------
Discussion at https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html

Please assess existing documentation for the impact of this Change.

Comment 1 Pete Travis 2015-01-10 17:58:56 UTC

The storage guide doesn't talk about thinp at all, we should cover it there.

Comment 3 Petr Bokoc 2019-11-07 15:30:00 UTC

I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.