diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2007-01-08 01:07:42 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2007-01-08 01:07:42 +0000 |
| commit | 9dc074bd3bf6c3bb30da34a2f1e88181429a7e7d (patch) | |
| tree | 08ddd0b2e60be756efe78f40e6bd068a4cf76dd8 /debian/README.checkarray | |
| parent | 575d35d4eea09ad9ff0edf487433e1fc474a5922 (diff) | |
added resync note
Diffstat (limited to 'debian/README.checkarray')
| -rw-r--r-- | debian/README.checkarray | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/debian/README.checkarray b/debian/README.checkarray index abc1c3db..9f691e6c 100644 --- a/debian/README.checkarray +++ b/debian/README.checkarray @@ -8,7 +8,8 @@ in the morning. This is realised by asking cron to wake up every Sunday with is less than or equal to 7. See #380425. 'check' is a read-only operation, even though the kernel logs may suggest -otherwise. +otherwise (e.g. /proc/mdstat and several kernel messages will mention +"resync"). Please also see question 21 of the FAQ. 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 @@ -17,6 +18,6 @@ However in the absence of read errors it is read-only. You can cancel a running array check with the -x option to checkarray. - -- martin f. krafft <madduck@debian.org> Fri, 06 Oct 2006 15:39:58 +0200 + -- martin f. krafft <madduck@debian.org> Mon, 08 Jan 2007 02:07:19 +0100 $Id$ |