summaryrefslogtreecommitdiff
path: root/debian/FAQ
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2007-01-08 01:04:12 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2007-01-08 01:04:12 +0000
commit6d003f6600d5123d9334278dce9b645b2dd45876 (patch)
tree37838dd9842f1ef1736e274eb6338d8f027a253c /debian/FAQ
parentb82ce0c6d88d02eae029a2bfb17922cac9a43a2c (diff)
resync note
Diffstat (limited to 'debian/FAQ')
-rw-r--r--debian/FAQ8
1 files changed, 8 insertions, 0 deletions
diff --git a/debian/FAQ b/debian/FAQ
index fefa05b3..3363b080 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -496,6 +496,14 @@ The latest version of this FAQ is available here:
I'll leave it up to you to figure things out. Now go read question 19.
+21. Why does the kernel speak of 'resync' when using checkarray
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ Please see README.checkarray and
+ http://www.mail-archive.com/linux-raid@vger.kernel.org/msg04835.html .
+
+ In short: it's a bug. checkarray is actually not a resync, but the kernel
+ does not distinguish between them.
+
-- martin f. krafft <madduck@debian.org> Thu, 30 Oct 2006 00:13:05 +0200
$Id$