diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2012-03-28 19:41:28 +0200 |
|---|---|---|
| committer | Alasdair G Kergon <agk@redhat.com> | 2012-03-28 19:41:28 +0200 |
| commit | c4a69ecdb463a901b4645230613961e134e897cd (patch) | |
| tree | c53e0a569f3d390ea2a97f964225d5383c6401ec /drivers/devfreq | |
| parent | dm persistent data: remove space map ref_count entries if redundant (diff) | |
| download | linux-c4a69ecdb463a901b4645230613961e134e897cd.tar.xz linux-c4a69ecdb463a901b4645230613961e134e897cd.zip | |
dm thin: relax hard limit on the maximum size of a metadata device
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>
Diffstat (limited to 'drivers/devfreq')
0 files changed, 0 insertions, 0 deletions