Bug 1371597
Summary: | DOCUMENTATION: cache volume extension doesn't work | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jonathan Earl Brassow <jbrassow> |
Component: | lvm2 | Assignee: | Jonathan Earl Brassow <jbrassow> |
lvm2 sub component: | Cache Logical Volumes | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | Steven J. Levine <slevine> |
Severity: | medium | ||
Priority: | unspecified | CC: | agk, cluster-qe, cmarthal, heinzm, jbrassow, lmiksik, msnitzer, prajnoha, prockai, thornber, zkabelac |
Version: | 7.2 | Keywords: | Documentation |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Release Note | |
Doc Text: |
Support for caching thinly-provisioned logical volumes with limitations
Red Hat Enterprise Linux 7.3 provides the ability to cache thinly provisioned logical volumes.
This brings caching benefits to all the thin logical volumes associated with a
particular thin pool. However, when thin pools are set up in this way, it is not currently possible to grow the thin pool without removing the cache layer first. This also means that thin pool auto-grow features are unavailable. Users should take care to monitor the fullness and consumption rate of their thin pools to avoid running out of space. Refer to the lvmthin(7) man page for information on thinly-provisioned logical volume and the lvmcache(7) man page for information on LVM cache volumes.
|
Story Points: | --- |
Clone Of: | 1251280 | Environment: | |
Last Closed: | 2016-09-19 21:06:17 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: | |||
Bug Depends On: | 1189111, 1233909, 1251280 | ||
Bug Blocks: |
Comment 1
Jonathan Earl Brassow
2016-08-30 15:16:45 UTC
Closing this bug now that the proper documentation is in the release notes. |