summaryrefslogtreecommitdiff
path: root/drivers/md/persistent-data/dm-space-map-disk.h
diff options
context:
space:
mode:
authorJoe Thornber <ejt@redhat.com>2014-01-07 19:49:02 +0400
committerMike Snitzer <snitzer@redhat.com>2014-01-08 06:05:18 +0400
commit7e664b3dec431eebf0c5df5ff704d6197634cf35 (patch)
tree2537389343636ffa174729b3a75f41080777711f /drivers/md/persistent-data/dm-space-map-disk.h
parent12c91a5c2d2a8e8cc40a9552313e1e7b0a2d9ee3 (diff)
downloadlinux-7e664b3dec431eebf0c5df5ff704d6197634cf35.tar.xz
dm space map metadata: fix extending the space map
When extending a metadata space map we should do the first commit whilst still in bootstrap mode -- a mode where all blocks get allocated in the new area. That way the commit overhead is allocated from the newly added space. Otherwise we risk running out of space. With this fix, and the previous commit "dm space map common: make sure new space is used during extend", the following device mapper testsuite test passes: dmtest run --suite thin-provisioning -n /resize_metadata_no_io/ Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Cc: stable@vger.kernel.org
Diffstat (limited to 'drivers/md/persistent-data/dm-space-map-disk.h')
0 files changed, 0 insertions, 0 deletions