summaryrefslogtreecommitdiff
path: root/drivers/md/persistent-data
diff options
context:
space:
mode:
authorJoe Thornber <ejt@redhat.com>2012-07-03 11:55:31 (GMT)
committerAlasdair G Kergon <agk@redhat.com>2012-07-03 11:55:31 (GMT)
commit0d200aefd4ac51787b6b80de1bb7ce93bccd59f6 (patch)
tree0a6da552aefa121af0856fb17da8cb6847d10342 /drivers/md/persistent-data
parent6887a4131da3adaab011613776d865f4bcfb5678 (diff)
downloadlinux-0d200aefd4ac51787b6b80de1bb7ce93bccd59f6.tar.xz
dm thin: commit metadata before creating metadata snapshot
Userland sometimes sees a corrupt metadata block if metadata is changing rapidly when a metadata snapshot is reserved for userland, To make the problem go away, commit before we take the metadata snapshot (which is a sensible thing to do anyway). The checksums mean userland spots this corruption immediately so there's no risk of acting on incorrect data. No corruption exists from the kernel's point of view, and thin_check passes after pool shutdown. I believe this is to do with shared blocks at the first level of the {device, mapping} btree. Prior to the metadata-snap support no sharing at this level was possible, so this patch is only required after commit cc8394d86f045b86ff303d3c9e4ce47d97148951 ("dm thin: provide userspace access to pool metadata"). Signed-off-by: Joe Thornber <ejt@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
Diffstat (limited to 'drivers/md/persistent-data')
0 files changed, 0 insertions, 0 deletions