| commit | cdbb4cc2e5c30895709163d8544057db21ee23e0 | |
| author | NeilBrown <neilb@cse.unsw.edu.au> | |
| Wed, 22 Jun 2005 00:17:18 +0000 (21 17:17 -0700) | ||
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | |
| Wed, 22 Jun 2005 02:07:44 +0000 (21 19:07 -0700) | ||
| tree | ca5037bfa8c51f61fe2c7627f2cbed37697af882 | treesnapshot (tar.gz zip) |
| parent | bc7f77de2cd81718dd789a2cfe68a7cf1b48f016 | commitdiff |
[PATCH] md: make sure md bitmap is cleared on a clean start.
As the array-wide clean bit (in the superblock) is set more agressively than
the bits in the bitmap are cleared, it is possible to have an array which is
clean despite there being bits set in the bitmap.
These bits will currently never get cleared, as they can only be cleared by a
resync pass, which never happens.
No, when reading bits from disk, be aware of whether the whole array is known
to be in sync, and act accordingly.
Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
As the array-wide clean bit (in the superblock) is set more agressively than
the bits in the bitmap are cleared, it is possible to have an array which is
clean despite there being bits set in the bitmap.
These bits will currently never get cleared, as they can only be cleared by a
resync pass, which never happens.
No, when reading bits from disk, be aware of whether the whole array is known
to be in sync, and act accordingly.
Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| drivers/md/bitmap.c | diffblobblamehistory |