summaryrefslogtreecommitdiff
path: root/Documentation/cciss.txt
diff options
context:
space:
mode:
authorStephen M. Cameron <steve.cameron@hp.com>2007-05-08 11:30:05 +0400
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-05-08 22:15:10 +0400
commit6c080f1a93591500299a514ef63209079ff007ac (patch)
tree1a8588ef48ec688d0f061d6fd2529d920aafa3ec /Documentation/cciss.txt
parentd3ed782458f315c30ea679b919a2cc59f2b82565 (diff)
downloadlinux-6c080f1a93591500299a514ef63209079ff007ac.tar.xz
Documentation: cciss: detecting failed drives
Document how to detect drive failures for cciss Signed-off-by: Stephen M. Cameron <steve.cameron@hp.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/cciss.txt')
-rw-r--r--Documentation/cciss.txt13
1 files changed, 10 insertions, 3 deletions
diff --git a/Documentation/cciss.txt b/Documentation/cciss.txt
index f74affe5c829..e65736c6b8bc 100644
--- a/Documentation/cciss.txt
+++ b/Documentation/cciss.txt
@@ -22,14 +22,21 @@ This driver is known to work with the following cards:
* 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: