diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-20 13:06:56 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-08-20 13:06:56 +0000 |
| commit | 0ff5de1c285abffc7dc28c253664eb983e07814d (patch) | |
| tree | 5adc404ee3dd057f1179009b2f2dc71898341ea6 /debian/README.checkarray | |
| parent | 6927024afecad1684464a974ff7e8c0fd4d05a21 (diff) | |
clarification
Diffstat (limited to 'debian/README.checkarray')
| -rw-r--r-- | debian/README.checkarray | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/debian/README.checkarray b/debian/README.checkarray index d034914a..386610f9 100644 --- a/debian/README.checkarray +++ b/debian/README.checkarray @@ -7,14 +7,14 @@ in the morning. This is realised by asking cron to wake up every Sunday with /etc/cron.d/mdadm, but then only running the script when the day of the month is less than or equal to 7. See #380425. -'check' is a read-only operation, even though the kernel logs may suggest +'check' is q read-only operation, even though the kernel logs may suggest otherwise. -If while reading, a read error occurs, the check will trigger the normal -response to read errors which is to generate the 'correct' data and try to -write that out - so it is possible that a 'check' will trigger a write. +If, however, while reading, a read error occurs, the check will trigger the +normal response to read errors which is to generate the 'correct' data and try +to write that out - so it is possible that a 'check' will trigger a write. However in the absence of read errors it is read-only. - -- martin f. krafft <madduck@debian.org> Tue, 01 Aug 2006 12:08:05 +0100 + -- martin f. krafft <madduck@debian.org> Tue, 20 Aug 2006 14:08:05 +0100 $Id$ |