Red Hat Bugzilla – Bug 1250934
fact that cachepool and origin must belong to one VG could/should be in the man...
Last modified: 2015-08-10 18:17:24 EDT
Description of problem:
it's important fact, would this had been in man I'd have saved some time.
Probably somewhere at the top.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Thanks, done here:
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:
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).