summaryrefslogtreecommitdiff
path: root/fs/exportfs
diff options
context:
space:
mode:
authorMike Snitzer <snitzer@redhat.com>2015-11-06 15:53:01 (GMT)
committerMike Snitzer <snitzer@redhat.com>2015-11-16 14:36:08 (GMT)
commit172c238612ebf81cabccc86b788c9209af591f61 (patch)
treeba97982ebd8f091062bfbf50b6cef15a4c7aa129 /fs/exportfs
parent8005c49d9aea74d382f474ce11afbbc7d7130bec (diff)
downloadlinux-172c238612ebf81cabccc86b788c9209af591f61.tar.xz
dm thin: restore requested 'error_if_no_space' setting on OODS to WRITE transition
A thin-pool that is in out-of-data-space (OODS) mode may transition back to write mode -- without the admin adding more space to the thin-pool -- if/when blocks are released (either by deleting thin devices or discarding provisioned blocks). But as part of the thin-pool's earlier transition to out-of-data-space mode the thin-pool may have set the 'error_if_no_space' flag to true if the no_space_timeout expires without more space having been made available. That implementation detail, of changing the pool's error_if_no_space setting, needs to be reset back to the default that the user specified when the thin-pool's table was loaded. Otherwise we'll drop the user requested behaviour on the floor when this out-of-data-space to write mode transition occurs. Reported-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Acked-by: Joe Thornber <ejt@redhat.com> Fixes: 2c43fd26e4 ("dm thin: fix missing out-of-data-space to write mode transition if blocks are released") Cc: stable@vger.kernel.org
Diffstat (limited to 'fs/exportfs')
0 files changed, 0 insertions, 0 deletions