From: NeilBrown Date: Thu, 7 Aug 2014 02:22:41 +0000 (+1000) Subject: md.4: replace "bad block log" with "bad block list" X-Git-Tag: mdadm-3.3.2~10 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=968d2a336ef0199155a6dced1624909180d29c9a;p=thirdparty%2Fmdadm.git md.4: replace "bad block log" with "bad block list" Elsewhere we use the term "list", and it is more accurate. Logs are usually append-only. This list isn't. Signed-off-by: NeilBrown --- diff --git a/md.4 b/md.4 index 722afbdb..e222237d 100644 --- a/md.4 +++ b/md.4 @@ -846,7 +846,7 @@ intent log if one is present. In 2.6.13, intent bitmaps are only supported with RAID1. Other levels with redundancy are supported from 2.6.15. -.SS BAD BLOCK LOG +.SS BAD BLOCK LIST From Linux 3.5 each device in an .I md @@ -856,7 +856,7 @@ and the data. When a block cannot be read and cannot be repaired by writing data recovered from other devices, the address of the block is stored in -the bad block log. Similarly if an attempt to write a block fails, +the bad block list. Similarly if an attempt to write a block fails, the address will be recorded as a bad block. If attempting to record the bad block fails, the whole device will be marked faulty. @@ -870,9 +870,9 @@ This allows an array to fail more gracefully - a few blocks on different devices can be faulty without taking the whole array out of action. -The log is particularly useful when recovering to a spare. If a few blocks +The list is particularly useful when recovering to a spare. If a few blocks cannot be read from the other devices, the bulk of the recovery can -complete and those few bad blocks will be recorded in the bad block log. +complete and those few bad blocks will be recorded in the bad block list. .SS WRITE-BEHIND