diff options
| author | NeilBrown | 2006-12-10 11:20:52 +0100 |
|---|---|---|
| committer | Linus Torvalds | 2006-12-10 18:57:21 +0100 |
| commit | 1757128438d41670ded8bc3bc735325cc07dc8f9 (patch) | |
| tree | e85679cbe949e337616ac53ab3b3fd1a3fa14a63 /fs/direct-io.c | |
| parent | [PATCH] md: return a non-zero error to bi_end_io as appropriate in raid5 (diff) | |
| download | kernel-qcow2-linux-1757128438d41670ded8bc3bc735325cc07dc8f9.tar.gz kernel-qcow2-linux-1757128438d41670ded8bc3bc735325cc07dc8f9.tar.xz kernel-qcow2-linux-1757128438d41670ded8bc3bc735325cc07dc8f9.zip | |
[PATCH] md: assorted md and raid1 one-liners
Fix few bugs that meant that:
- superblocks weren't alway written at exactly the right time (this
could show up if the array was not written to - writting to the array
causes lots of superblock updates and so hides these errors).
- restarting device recovery after a clean shutdown (version-1 metadata
only) didn't work as intended (or at all).
1/ Ensure superblock is updated when a new device is added.
2/ Remove an inappropriate test on MD_RECOVERY_SYNC in md_do_sync.
The body of this if takes one of two branches depending on whether
MD_RECOVERY_SYNC is set, so testing it in the clause of the if
is wrong.
3/ Flag superblock for updating after a resync/recovery finishes.
4/ If we find the neeed to restart a recovery in the middle (version-1
metadata only) make sure a full recovery (not just as guided by
bitmaps) does get done.
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions