Bug 1398865 - LVM docs incorrectly mention snapshot tagging as not possible.
Summary: LVM docs incorrectly mention snapshot tagging as not possible.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: Documentation
Version: 5.11
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: RHEL DPM
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-26 19:27 UTC by John Pittman
Modified: 2019-12-16 07:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-30 14:20:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2779931 0 None None None 2016-11-26 19:40:21 UTC

Description John Pittman 2016-11-26 19:27:41 UTC 
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Logical_Volume_Manager_Administration/lvm_tags.html

Section Number and Name: 

Appendix C. LVM Object Tags

Describe the issue: 

"Only objects in a volume group can be tagged. Physical volumes lose their tags if they are removed from a volume group; this is because tags are stored as part of the volume group metadata and that is deleted when a physical volume is removed. Snapshots cannot be tagged."

Per https://www.redhat.com/archives/linux-lvm/2012-April/msg00032.html this works and is supported.

Suggestions for improvement: 

Remove the last sentence from the mentioned paragraph.
Comment 2 Steven J. Levine 2016-11-30 14:20:10 UTC 
The RHEL 5 version of this document on the Portal no longer says that tagging is not supported for snapshots.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Logical_Volume_Manager_Administration/lvm_tags.html
Note You need to log in before you can comment on or make changes to this bug.