diff options
author | Ian Dall <ian@beware.dropbear.id.au> | 2007-07-09 11:29:04 +1000 |
---|---|---|
committer | Neil Brown <neilb@suse.de> | 2007-07-09 11:29:04 +1000 |
commit | 7d19ad0de31cd0b94e69ac5f2efee98254f27316 (patch) | |
tree | 60c296afcfd59fb38264cd5bf09980535536f356 /mdadm.c | |
parent | 66f8bbbe90de9cced56a0c6062ef106503ef04c1 (diff) | |
download | mdadm-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.
Diffstat (limited to 'mdadm.c')
-rw-r--r-- | mdadm.c | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -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; |