summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-03-19 12:46:37 +1100
committerNeilBrown <neilb@suse.de>2012-03-19 12:46:37 +1100
commitc744a65c1e2d59acc54333ce80a5b0702a98010b (patch)
treec76ff42e8f799030636d07c82879cc2bef7798db /Documentation
parentdc10c643e8a8d008fd16dd6706e9e0018eadf8d2 (diff)
downloadop-kernel-dev-c744a65c1e2d59acc54333ce80a5b0702a98010b.zip
op-kernel-dev-c744a65c1e2d59acc54333ce80a5b0702a98010b.tar.gz
md: don't set md arrays to readonly on shutdown.
It seems that with recent kernel, writeback can still be happening while shutdown is happening, and consequently data can be written after the md reboot notifier switches all arrays to read-only. This causes a BUG. So don't switch them to read-only - just mark them clean and set 'safemode' to '2' which mean that immediately after any write the array will be switch back to 'clean'. This could result in the shutdown happening when array is marked dirty, thus forcing a resync on reboot. However if you reboot without performing a "sync" first, you get to keep both halves. This is suitable for any stable kernel (though there might be some conflicts with obvious fixes in earlier kernels). Cc: stable@vger.kernel.org Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud