The patch titled
Documentation: cciss: detecting failed drives
has been added to the -mm tree. Its filename is
documentation-cciss-detecting-failed-drives.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Documentation: cciss: detecting failed drives
From: Stephen M. Cameron <steve.cameron@xxxxxx>
Document how to detect drive failures for cciss
Signed-off-by: Stephen M. Cameron <steve.cameron@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/cciss.txt | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff -puN Documentation/cciss.txt~documentation-cciss-detecting-failed-drives Documentation/cciss.txt
--- a/Documentation/cciss.txt~documentation-cciss-detecting-failed-drives
+++ a/Documentation/cciss.txt
@@ -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:
_
Patches currently in -mm which might be from steve.cameron@xxxxxx are
cciss-reformat-error-handling.patch
cciss-add-sg_io-ioctl-to-cciss.patch
cciss-set-rq-errors-more-correctly-in-driver.patch
cciss-include-scsi-scsih-unconditionally.patch
documentation-cciss-detecting-failed-drives.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
