diff options
author | NeilBrown <neilb@suse.de> | 2009-12-14 12:49:56 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-12-14 12:51:41 +1100 |
commit | ece5cff0da9e696c360fff592cb5f51b6419e4d6 (patch) | |
tree | 1c5cab0e89ae466be9edb476ceb91e5c898fafa6 /Documentation/md.txt | |
parent | 624ce4f5658fa3e0303c1217bba2706142fe7568 (diff) | |
download | linux-stable-ece5cff0da9e696c360fff592cb5f51b6419e4d6.tar.gz linux-stable-ece5cff0da9e696c360fff592cb5f51b6419e4d6.tar.bz2 linux-stable-ece5cff0da9e696c360fff592cb5f51b6419e4d6.zip |
md: Support write-intent bitmaps with externally managed metadata.
In this case, the metadata needs to not be in the same
sector as the bitmap.
md will not read/write any bitmap metadata. Config must be
done via sysfs and when a recovery makes the array non-degraded
again, writing 'true' to 'bitmap/can_clear' will allow bits in
the bitmap to be cleared again.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'Documentation/md.txt')
-rw-r--r-- | Documentation/md.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/Documentation/md.txt b/Documentation/md.txt index 18fad6876228..21d26fb5d02b 100644 --- a/Documentation/md.txt +++ b/Documentation/md.txt @@ -322,6 +322,22 @@ All md devices contain: 'backlog' sets a limit on the number of concurrent background writes. If there are more than this, new writes will by synchronous. + bitmap/metadata + This can be either 'internal' or 'external'. + 'internal' is the default and means the metadata for the bitmap + is stored in the first 256 bytes of the allocated space and is + managed by the md module. + 'external' means that bitmap metadata is managed externally to + the kernel (i.e. by some userspace program) + bitmap/can_clear + This is either 'true' or 'false'. If 'true', then bits in the + bitmap will be cleared when the corresponding blocks are thought + to be in-sync. If 'false', bits will never be cleared. + This is automatically set to 'false' if a write happens on a + degraded array, or if the array becomes degraded during a write. + When metadata is managed externally, it should be set to true + once the array becomes non-degraded, and this fact has been + recorded in the metadata. |