summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid10.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-10-11 05:19:39 +0200
committerNeilBrown <neilb@suse.de>2012-10-11 05:19:39 +0200
commit48c26ddc9f85808632a63b3ae50b868c86a2435f (patch)
tree2d4f5d9f299f4be2c7b137655a0daae01e659a9a /drivers/md/raid10.c
parentSubject: [PATCH] md:change resync_mismatches to atomic64_t to avoid races (diff)
downloadlinux-48c26ddc9f85808632a63b3ae50b868c86a2435f.tar.xz
linux-48c26ddc9f85808632a63b3ae50b868c86a2435f.zip
md: writing to sync_action should clear the read-auto state.
In some cases array are started in 'read-auto' state where in nothing gets written to any device until the array is written to. The purpose of this is to make accidental auto-assembly of the wrong arrays less of a risk, and to allow arrays to be started to read suspend-to-disk images without actually changing anything (as might happen if the array were dirty and a resync seemed necessary). Explicitly writing the 'sync_action' for a read-auto array currently doesn't clear the read-auto state, so the sync action doesn't happen, which can be confusing. So allow any successful write to sync_action to clear any read-auto state. Reported-by: Alexander Kühn <alexander.kuehn@nagilum.de> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions