summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIan Dall <ian@beware.dropbear.id.au>2007-07-09 11:29:04 +1000
committerNeil Brown <neilb@suse.de>2007-07-09 11:29:04 +1000
commit7d19ad0de31cd0b94e69ac5f2efee98254f27316 (patch)
tree60c296afcfd59fb38264cd5bf09980535536f356
parent66f8bbbe90de9cced56a0c6062ef106503ef04c1 (diff)
downloadmdadm-7d19ad0de31cd0b94e69ac5f2efee98254f27316.tar.gz
mdadm-7d19ad0de31cd0b94e69ac5f2efee98254f27316.tar.xz
mdadm-7d19ad0de31cd0b94e69ac5f2efee98254f27316.zip
Allow "--write-behind=" to be done in grow mode.
From: Ian Dall <ian@beware.dropbear.id.au> I have a small patch to mdadm which allows the write-behind amount to be set a array grow time (instead of currently only at grow or create time). I have tested this fairly extensively on some arrays built out of loop back devices, and once on a real live array.
-rw-r--r--ChangeLog3
-rw-r--r--mdadm.c1
2 files changed, 4 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index e34a6b9..10ddcf0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,6 @@
+Changes Prior to this release
+ - allow --write-behind to be set for --grow.
+
Changes Prior to 2.6.2 release
- --fail detached and --remove faulty can be used to fail and
remove devices that are no longer physically present.
diff --git a/mdadm.c b/mdadm.c
index e96ce68..45ffaee 100644
--- a/mdadm.c
+++ b/mdadm.c
@@ -844,6 +844,7 @@ int main(int argc, char *argv[])
bitmap_chunk = bitmap_chunk ? bitmap_chunk * 1024 : 512;
continue;
+ case O(GROW, WriteBehind):
case O(BUILD, WriteBehind):
case O(CREATE, WriteBehind): /* write-behind mode */
write_behind = DEFAULT_MAX_WRITE_BEHIND;