[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20070417195747.GA11004@quandary.cca.cpqcorp.net>
Date: Tue, 17 Apr 2007 14:57:47 -0500
From: Stephen Cameron <steve.cameron@...com>
To: linux-kernel@...r.kernel.org
Cc: mike.miller@...com
Subject: [PATCH] Documentation: cciss: detecting failed drives
From: Stephen M. Cameron <steve.cameron@...com>
Signed-off-by: Stephen M. Cameron <steve.cameron@...com>
Document how to detect drive failures for cciss
---
Documentation/cciss.txt | 13 ++++++++++---
1 files changed, 10 insertions(+), 3 deletions(-)
diff -puN Documentation/cciss.txt~cciss_vol_status_doc Documentation/cciss.txt
--- linux-2.6.21-rc6/Documentation/cciss.txt~cciss_vol_status_doc 2007-04-13 13:56:17.000000000 -0500
+++ linux-2.6.21-rc6-scameron/Documentation/cciss.txt 2007-04-13 14:01:33.000000000 -0500
@@ -22,14 +22,21 @@ This driver is known to work with the fo
* SA E200i
* SA E500
-If nodes are not already created in the /dev/cciss directory, run as root:
+Detecting drive failures:
+-------------------------
-# cd /dev
-# ./MAKEDEV cciss
+To get the status of logical volumes and to detect physical drive
+failures, you can use the cciss_vol_status program found here:
+http://cciss.sourceforge.net/#cciss_utils
Device Naming:
--------------
+If nodes are not already created in the /dev/cciss directory, run as root:
+
+# cd /dev
+# ./MAKEDEV cciss
+
You need some entries in /dev for the cciss device. The MAKEDEV script
can make device nodes for you automatically. Currently the device setup
is as follows:
_
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists