c4a69ecdb4
The thin metadata format can only make use of a device that is <= THIN_METADATA_MAX_SECTORS (currently 15.9375 GB). Therefore, there is no practical benefit to using a larger device. However, it may be that other factors impose a certain granularity for the space that is allocated to a device (E.g. lvm2 can impose a coarse granularity through the use of large, >= 1 GB, physical extents). Rather than reject a larger metadata device, during thin-pool device construction, switch to allowing it but issue a warning if a device larger than THIN_METADATA_MAX_SECTORS_WARNING (16 GB) is provided. Any space over 15.9375 GB will not be used. Signed-off-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com> |
||
---|---|---|
.. | ||
delay.txt | ||
dm-crypt.txt | ||
dm-flakey.txt | ||
dm-io.txt | ||
dm-log.txt | ||
dm-queue-length.txt | ||
dm-raid.txt | ||
dm-service-time.txt | ||
dm-uevent.txt | ||
kcopyd.txt | ||
linear.txt | ||
persistent-data.txt | ||
snapshot.txt | ||
striped.txt | ||
thin-provisioning.txt | ||
zero.txt |