summaryrefslogtreecommitdiffstats
path: root/man4/cciss.4
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
commit3af6d22bb3850ab2bac67287e3a3d3b0e32868e5 (patch)
tree3ee7a3ec64525911fa865bb984c86d997d855527 /man4/cciss.4
parentAdding debian version 6.05.01-1. (diff)
downloadmanpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.tar.xz
manpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.zip
Merging upstream version 6.7.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'man4/cciss.4')
-rw-r--r--man4/cciss.440
1 files changed, 20 insertions, 20 deletions
diff --git a/man4/cciss.4 b/man4/cciss.4
index 9194c8a..6b6a6d1 100644
--- a/man4/cciss.4
+++ b/man4/cciss.4
@@ -6,7 +6,7 @@
.\"
.\" shorthand for double quote that works everywhere.
.ds q \N'34'
-.TH cciss 4 2023-05-03 "Linux man-pages 6.05.01"
+.TH cciss 4 2023-10-31 "Linux man-pages 6.7"
.SH NAME
cciss \- HP Smart Array block driver
.SH SYNOPSIS
@@ -20,7 +20,7 @@ This obsolete driver was removed in Linux 4.14,
as it is superseded by the
.BR hpsa (4)
driver in newer kernels.
-.PP
+.P
.B cciss
is a block driver for older HP Smart Array RAID controllers.
.SS Options
@@ -32,7 +32,7 @@ driver from attempting to drive any controllers that the
driver is capable of controlling, which is to say, the
.B cciss
driver is restricted by this option to the following controllers:
-.PP
+.P
.nf
Smart Array 5300
Smart Array 5i
@@ -56,7 +56,7 @@ driver is restricted by this option to the following controllers:
The
.B cciss
driver supports the following Smart Array boards:
-.PP
+.P
.nf
Smart Array 5300
Smart Array 5i
@@ -95,7 +95,7 @@ run from the Smart Array's option ROM at boot time.
.SH FILES
.SS Device nodes
The device naming scheme is as follows:
-.PP
+.P
Major numbers:
.IP
.TS
@@ -109,9 +109,9 @@ r r.
110 cciss6
111 cciss7
.TE
-.PP
+.P
Minor numbers:
-.PP
+.P
.EX
b7 b6 b5 b4 b3 b2 b1 b0
|\-\-\-\-+\-\-\-\-| |\-\-\-\-+\-\-\-\-|
@@ -120,7 +120,7 @@ Minor numbers:
|
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- Logical Volume number
.EE
-.PP
+.P
The device naming scheme is:
.TS
li l.
@@ -140,7 +140,7 @@ The files
contain information about
the configuration of each controller.
For example:
-.PP
+.P
.in +4n
.EX
$ \fBcd /proc/driver/cciss\fP
@@ -237,7 +237,7 @@ for more details.)
You must enable "SCSI tape drive support for Smart Array 5xxx" and
"SCSI support" in your kernel configuration to be able to use SCSI
tape drives with your Smart Array 5xxx controller.
-.PP
+.P
Additionally, note that the driver will not engage the SCSI core at
init time.
The driver must be directed to dynamically engage the SCSI core via the
@@ -255,7 +255,7 @@ This is best done via an initialization script
.IR /etc/init.d ,
but could vary depending on distribution).
For example:
-.PP
+.P
.in +4n
.EX
for x in /proc/driver/cciss/cciss[0\-9]*
@@ -264,10 +264,10 @@ do
done
.EE
.in
-.PP
+.P
Once the SCSI core is engaged by the driver, it cannot be disengaged
(except by unloading the driver, if it happens to be linked as a module.)
-.PP
+.P
Note also that if no sequential access devices or medium changers are
detected, the SCSI core will not be engaged by the action of the above
script.
@@ -283,7 +283,7 @@ filesystem.
For example:
.IP
echo "rescan" > /proc/scsi/cciss0/1
-.PP
+.P
This causes the driver to:
.RS
.IP (1) 5
@@ -293,20 +293,20 @@ physical SCSI buses and/or fiber channel arbitrated loop, and
make note of any new or removed sequential access devices
or medium changers.
.RE
-.PP
+.P
The driver will output messages indicating which
devices have been added or removed and the controller, bus, target, and
lun used to address each device.
The driver then notifies the SCSI midlayer
of these changes.
-.PP
+.P
Note that the naming convention of the
.I /proc
filesystem entries
contains a number in addition to the driver name
(e.g., "cciss0"
instead of just "cciss", which you might expect).
-.PP
+.P
Note:
.I Only
sequential access devices and medium changers are presented
@@ -340,7 +340,7 @@ If that doesn't work, the device is reset.
If that doesn't work, the SCSI bus is reset.
.IP (4)
If that doesn't work, the host bus adapter is reset.
-.PP
+.P
The
.B cciss
driver is a block
@@ -358,7 +358,7 @@ in aborting commands, and sometimes it appears they will not even
obey a reset command, though in most circumstances they will.
If the command cannot be aborted and the device cannot be
reset, the device will be set offline.
-.PP
+.P
In the event that the error-handling code is triggered and a tape drive is
successfully reset or the tardy command is successfully aborted, the
tape drive may still not allow I/O to continue until some command
@@ -371,7 +371,7 @@ for example) before I/O can proceed again to a tape drive that was reset.
.BR cciss_vol_status (8),
.BR hpacucli (8),
.BR hpacuxe (8)
-.PP
+.P
.UR http://cciss.sf.net
.UE ,
and