RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

..no?
it's important fact, would this had been in man I'd have saved some time.
Probably somewhere at the top.

regards

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Thanks, done here:
https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=1c013e7ae29a9e3aa20930a24f3fcf0637ef1e91

This applies to all types of LVs and I am not sure this deserves a special treatment for caching or whether it is desirable to repeat this for mirrors, thin-pools.

This should be considered a corner stone of LVM. Perhaps a lvm(7) (or LVM(7)) man page would be a better place. Something like the LVM-HOWTO.

(Reopen and create a documentation tracker bug) or (keep closed)?

having no knowledge of inner workings of LVM one would presume, as I did that a cachepool is somehow special and maybe it's even better! to keep it on a separate.

I'd put it there for each man, I may skip, again as I did other docs and try the shortest possible path, like everybody would do, straight to the goal, so I only looked at lvmcache.

I know you guys do not think about these things for it's like a gravity, for the rest of us - it can save a heck lot of time.

Recently added the last sentence in the description:
http://man7.org/linux/man-pages/man7/lvmcache.7.html

I have added that same sentence to the description of LVM cache volumes in the LVM manual.

To clarify Comment 6: This will be in the 7.2 version of the document, and the 6.8 version going forward (or if the 6.7 version gets repushed to the Customer Portal).