Startseite Erkunden Hilfe
Registrieren Anmelden
phyus
/
linux-vybrid_public
8
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Struktur: 50a845700b
Branches Tags
linux-vybrid_pu...
/
Documentation
Linus Torvalds 85082fd7cb Merge branch 'for-linus' of master.kernel.org:/home/rmk/linux-2.6-arm vor 17 Jahren
..
ABI a3da5bf84a Merge branch 'x86/for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip vor 17 Jahren
DocBook a606b5e24b kgdb: documentation update - remove kgdboe vor 17 Jahren
PCI 4b5ff46923 PCI: doc/pci: create Documentation/PCI/ and move files into it vor 17 Jahren
RCU b5606c2d44 remove final fastcall users vor 17 Jahren
accounting f93f18cd94 Update taskstats-struct document for scaled time accounting vor 17 Jahren
acpi 9a9e0d6855 ACPI: Remove ACPI_CUSTOM_DSDT_INITRD option vor 17 Jahren
aoe 262bf54144 aoe: user can ask driver to forget previously detected devices vor 17 Jahren
arm 71d54f3855 [MTD] [NAND] S3C2410 Large page NAND support vor 17 Jahren
auxdisplay 450c622e9f Miguel Ojeda has moved vor 17 Jahren
blackfin 474f1a667d Blackfin arch: kgdb specific code vor 18 Jahren
block c1c72b5994 block: Data integrity infrastructure documentation vor 17 Jahren
cdrom 0a0c4114df cdrom: make unregister_cdrom() return void vor 17 Jahren
connector dd00cc486a some kmalloc/memset ->kzalloc (tree wide) vor 18 Jahren
console 4b8a8b812e Typo: fro -> from vor 18 Jahren
controllers d823f6bfec devcgroup: fix odd behaviour when writing 'a' to devices.allow vor 17 Jahren
cpu-freq da8395be0b [CPUFREQ] Remove documentation of removed ondemand tunable. vor 17 Jahren
cpuidle fe8e288a63 cpuidle: Add Documentation vor 17 Jahren
cris 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
crypto 86f578de5b [CRYPTO] doc: Update api-intro.txt vor 17 Jahren
device-mapper e3dcc5a387 dm crypt: add documentation vor 17 Jahren
driver-model 44414e14af Driver core: Update some prototypes in platform.txt vor 17 Jahren
dvb 3869007812 V4L/DVB (7077): bt878: remove handcrafted PCI subsystem ID check vor 17 Jahren
early-userspace fda6ab8bbe Documentation: Remove last references to BitKeeper. vor 17 Jahren
fault-injection 185848707e fault-injection: fix example scripts in documentation vor 18 Jahren
fb 0e170c72c0 fbdev: intelfb: add support for the Intel Integrated Graphics Controller 965G/965GM vor 17 Jahren
filesystems 883eed1b3e Merge branch 'pci-for-jesse' of git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip into for-linus vor 17 Jahren
firmware_class d289bf7bdd firmware: move firmware_class from Documentation/ to samples/ vor 17 Jahren
frv 0868ff7a42 move frv docs one level up vor 17 Jahren
hwmon 125ff8087f hwmon: Update the sysfs interface documentation vor 17 Jahren
i2c 2260e63a2f i2c: Documentation: fix device matching description vor 17 Jahren
i2o be2a608bd0 documentation: convert the Documentation directory to UTF-8 vor 18 Jahren
ia64 fdae862f91 KVM: ia64: Add a guide about how to create kvm guests on ia64 vor 17 Jahren
ide 9dcba7f2b7 gayle: add "doubler" parameter vor 17 Jahren
infiniband 2be8e3ee8e IB/umad: Add P_Key index support vor 17 Jahren
input e32f7ee876 Input: add keyboard notifier documentation vor 17 Jahren
ioctl cf1b939e41 [PATCH] Document how to decode an IOCTL number vor 18 Jahren
isdn 0f035b8e84 spelling fixes: Documentation/ vor 17 Jahren
ja_JP 82bd3f17f4 Fix broken utf-8 encodings in ja_JP translation of stable_kernel_rules.txt vor 17 Jahren
kbuild 2cb1e1257f kconfig-language.txt: remove bogus hint vor 17 Jahren
kdump 068b453834 x86: fix documentation bug about relocatability vor 17 Jahren
ko_KR ba3882a917 HOWTO: update misspelling and word incorrected vor 17 Jahren
laptops 197a2cd907 thinkpad-acpi: SW_RADIO to SW_RFKILL_ALL rename vor 17 Jahren
lguest 2088761152 lguest: notify on empty vor 17 Jahren
m68k f37a7238d3 [SCSI] 53c7xx: fix removal fallout vor 17 Jahren
make 451ad114c6 Documentation/make/headers_install.txt vor 17 Jahren
mips f629b38bed au1xxx-ide: fix MWDMA support vor 17 Jahren
mn10300 b920de1b77 mn10300: add the MN10300/AM33 architecture to the kernel vor 17 Jahren
namespaces 2868f89fc4 The namespaces compatibility list doc vor 17 Jahren
netlabel 59c51591a0 Fix occurrences of "the the " vor 18 Jahren
networking 4edc2f3416 ip: sysctl documentation cleanup vor 17 Jahren
parisc 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
pcmcia 906da809c5 pcmcia: replace kio_addr_t with unsigned int everywhere vor 17 Jahren
power 58aca23226 PM: Handle device registrations during suspend/resume vor 17 Jahren
powerpc 80791be111 [POWERPC] mpc5200: Allow for fixed speed MII configurations vor 17 Jahren
prctl f132697326 generic, x86: add tests for prctl PR_GET_TSC and PR_SET_TSC vor 17 Jahren
s390 139b83dd57 [S390] cio: Remove cio_msg kernel parameter. vor 17 Jahren
scheduler f7d62364b2 sched: fix typo in Documentation/scheduler/sched-rt-group.txt vor 17 Jahren
scsi 127ce971ad [SCSI] megaraid_sas; Update the Version and Changelog vor 17 Jahren
serial 89f3da3e06 [SERIAL] Update parity handling documentation vor 19 Jahren
sh 1929cb340b sh: SH7722 clock framework support. vor 18 Jahren
sound 8c53b96f22 ALSA: hda - Add description of bdl_pos_adj option vor 17 Jahren
sparc fa7744dbb6 [SPARC/64]: Prepare to remove of_platform_driver name. vor 17 Jahren
spi 31a1629426 documentation: move spidev_fdx example to its own source file vor 17 Jahren
sysctl ac76cff2ec Documentation: sysctl/kernel.txt: fix documentation reference vor 17 Jahren
telephony 51448e2ad7 Add a 00-INDEX file to Documentation/telephony/ vor 17 Jahren
thermal e9ae71078b thermal: update the documentation vor 17 Jahren
timers 3833eecc18 Documentation: move timer related documentation to a single place vor 17 Jahren
tracers 6f6f394d9c doc: update mmiotrace doc to current status vor 17 Jahren
uml 4ae0edc21b Fix typos in /Documentation : 'U-Z' vor 18 Jahren
usb 08177e12b7 USB: add documentation about callbacks vor 17 Jahren
video4linux 104fe9a2d2 V4L/DVB (8043): au0828: add support for additional USB device id's vor 17 Jahren
vm cde5353599 Christoph has moved vor 17 Jahren
w1 ad8dc96e3b w1-gpio: add GPIO w1 bus master driver vor 17 Jahren
watchdog 0d710cba3a [WATCHDOG] clarify watchdog operation in documentation vor 17 Jahren
x86 200001eb14 x86 boot: only pick up additional EFI memmap if add_efi_memmap flag vor 17 Jahren
zh_CN 463e526083 Chinese: add translation of Codingstyle vor 17 Jahren
00-INDEX 753d7054c3 documentation: remove smart-config.txt vor 17 Jahren
BUG-HUNTING dcc85cb618 Documentation: add hint about call traces & module symbols to BUG-HUNTING vor 17 Jahren
Changes c3887cd725 [x86 setup] Document grub < 0.93 as broken vor 18 Jahren
CodingStyle dff4982f5c CodingStyle: relax the 80-cole rule vor 17 Jahren
DMA-API.txt 02d15c4322 doc: fix DMA-API function parameters vor 17 Jahren
DMA-ISA-LPC.txt fa00e7e152 Fix typos in /Documentation : 'T'' vor 18 Jahren
DMA-attributes.txt a75b0a2f68 dma: document dma_*map*_attrs() interfaces vor 17 Jahren
DMA-mapping.txt 2768f92c06 doc: replace yet another dev with pdev for consistency in DMA-mapping.txt vor 17 Jahren
HOWTO 0302c01b4b Documentation/HOWTO: correct wrong kernel bugzilla FAQ URL vor 17 Jahren
IO-mapping.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
IPMI.txt 612b5a8d3a IPMI: new NMI handling vor 17 Jahren
IRQ-affinity.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
IRQ.txt f702d7013c [PATCH] genirq: irq: document what an IRQ is vor 19 Jahren
Intel-IOMMU.txt e820482cd2 Intel IOMMU: Iommu Gfx workaround vor 17 Jahren
MSI-HOWTO.txt 4904e23b6b PCI: Remove no longer correct documentation regarding MSI vector assignment vor 17 Jahren
ManagementStyle 9ca2152e17 Fix this Paul Simon song's name vor 17 Jahren
README.DAC960 890fbae281 [PATCH] devfs: Last little devfs cleanups throughout the kernel tree. vor 19 Jahren
README.cycladesZ 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
SAK.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
SM501.txt f0ae5669be Tweak Documentation/SM501.txt vor 17 Jahren
SecurityBugs 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
Smack.txt e114e47377 Smack: Simplified Mandatory Access Control Kernel vor 17 Jahren
SubmitChecklist df24d9a6a9 Documentation: prune redundant SubmitChecklist items vor 17 Jahren
SubmittingDrivers 507a6a8c9b Update 2.4 maintainer in document vor 17 Jahren
SubmittingPatches adbd5886da doc: add suggestions about good practises for maintainers vor 17 Jahren
VGA-softcursor.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
applying-patches.txt c594a50db4 [PATCH] Docs update: typos, corrections and additions to applying-patches.txt vor 19 Jahren
atomic_ops.txt 02c608c1fe documentation: atomic_add_unless() doesn't imply mb() on failure vor 17 Jahren
basic_profiling.txt 0c0a400d1d [PATCH] oprofile: report anonymous region samples vor 20 Jahren
binfmt_misc.txt be2a608bd0 documentation: convert the Documentation directory to UTF-8 vor 18 Jahren
braille-console.txt f7511d5f66 Basic braille screen reader support vor 17 Jahren
cachetlb.txt 1c7037db50 remove unused flush_tlb_pgtables vor 17 Jahren
cciss.txt 24aac480e7 cciss: add new hardware support vor 17 Jahren
cgroups.txt bef67c5a7d cgroups: document the effect of attaching PID 0 to a cgroup vor 17 Jahren
cli-sti-removal.txt c0d1f29534 DOCUMENTATION: Use newer DEFINE_SPINLOCK macro in docs. vor 17 Jahren
computone.txt bf6ee0ae49 remove mentionings of devfs in documentation vor 18 Jahren
cpqarray.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
cpu-hotplug.txt 48483b3290 [S390] Get rid of additional_cpus kernel parameter. vor 17 Jahren
cpu-load.txt 48dba8ab9b [PATCH] Documentation: CPU load calculation description vor 18 Jahren
cpusets.txt 46b6d94eb0 doc: document the relax_domain_level kernel boot argument vor 17 Jahren
cputopology.txt fff9289b21 Fix typos in Documentation/: 'D'-'E' vor 18 Jahren
dcdbas.txt 90563ec412 [PATCH] dcdbas: add Dell Systems Management Base Driver with sysfs support vor 19 Jahren
debugging-modules.txt 0cadfc0953 Documentation: Clarify when module debugging actually works. vor 17 Jahren
debugging-via-ohci1394.txt 080de8c2c5 firewire: fw-ohci: add option for remote debugging vor 17 Jahren
dell_rbu.txt 992caacf11 Fix typos in Documentation/: 'N'-'P' vor 18 Jahren
devices.txt 01dd2fbf0d typo fixes vor 17 Jahren
digiepca.txt 0418726bb5 typo fixes: aquire -> acquire vor 19 Jahren
dontdiff beda8ae716 dontdiff: ignore timeconst.h vor 17 Jahren
edac.txt 4a6b88ca3d move edac.txt two levels up vor 17 Jahren
eisa.txt 4ae0edc21b Fix typos in /Documentation : 'U-Z' vor 18 Jahren
email-clients.txt 8f1466ff0a email-clients.txt: sylpheed is OK at IMAP vor 17 Jahren
exception.txt 670e9f34ee Documentation: remove duplicated words vor 18 Jahren
feature-removal-schedule.txt 16d7523973 thermal: Create CONFIG_THERMAL_HWMON=n vor 17 Jahren
floppy.txt 98766fbe60 [PATCH] kernel Doc/ URL corrections vor 19 Jahren
ftrace.txt a41eebab75 ftrace: document updates vor 17 Jahren
gpio.txt e6de1808f8 gpio: define gpio_is_valid() vor 17 Jahren
hayes-esp.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
highuid.txt ec98c6b9b4 [SPARC]: Remove SunOS and Solaris binary support. vor 17 Jahren
hpet.txt 07ff8ee79e hpet.txt: broken link fix vor 18 Jahren
hw_random.txt 537878d2c9 hw_random doc updates vor 17 Jahren
initrd.txt a7b1a68b25 use the newc archive format as requested by initramfs vor 17 Jahren
io_ordering.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
ioctl-number.txt 9d92a7e1b0 [S390] cio: Add chsc subchannel driver. vor 17 Jahren
iostats.txt 0e53c2be04 Enhanced partition statistics: documentation update vor 17 Jahren
irqflags-tracing.txt 55df314fbd [PATCH] lockdep: irqtrace subsystem, docs vor 19 Jahren
isapnp.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
java.txt 59dd24d32c Documentation/java.txt: typo and grammar fixes vor 17 Jahren
kernel-doc-nano-HOWTO.txt 0842b245a8 doc: document the kernel-doc conventions for kernel hackers vor 17 Jahren
kernel-docs.txt 34397892a3 doc: update to URL and status of kernel-docs.txt entry vor 17 Jahren
kernel-parameters.txt 85082fd7cb Merge branch 'for-linus' of master.kernel.org:/home/rmk/linux-2.6-arm vor 17 Jahren
keys-request-key.txt 4a38e122e2 keys: allow the callout data to be passed as a blob rather than a string vor 17 Jahren
keys.txt 0b77f5bfb4 keys: make the keyring quotas controllable through /proc/sys vor 17 Jahren
kobject.txt acccafe9ca kobject: Documentation Spelling Patch vor 17 Jahren
kprobes.txt 3b0cb4caef kprobes: update document about batch registration vor 17 Jahren
kref.txt 1373bed34e docs: convert kref semaphore to mutex vor 17 Jahren
ldm.txt dde33348e5 LDM: Fix for Windows Vista dynamic disks vor 18 Jahren
leds-class.txt 0013b23d66 leds: disable triggers on brightness set vor 17 Jahren
local_ops.txt 34aebfd3bd Revert "local_t Documentation update" vor 17 Jahren
lockdep-design.txt 5fcce7432a [PATCH] fix lockdep-design.txt vor 18 Jahren
lockstat.txt a560aa48ee lockstat: documentation vor 17 Jahren
logo.gif 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
logo.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
magic-number.txt ec98c6b9b4 [SPARC]: Remove SunOS and Solaris binary support. vor 17 Jahren
markers.txt 5f9468cebf Linux Kernel Markers: document format string vor 17 Jahren
mca.txt 2af3e6017e The ps2esdi driver was marked as BROKEN more than two years ago due to being vor 17 Jahren
md.txt 8b3e6cdc53 md: introduce get_priority_stripe() to improve raid456 write performance vor 17 Jahren
memory-barriers.txt 73f10281ea read_barrier_depends arch fixlets vor 17 Jahren
memory-hotplug.txt 10020ca246 memory hotplug: document the memory hotplug notifier vor 17 Jahren
memory.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
mono.txt 84eb8d0608 Fix "can not" in Documentation and Kconfig vor 18 Jahren
moxa-smartio 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
mtrr.txt 235963b2ed [PATCH] Doc: fix mtrr userspace programs to build cleanly vor 19 Jahren
mutex-design.txt 343b901980 Documentation: Add nested versions of mutex locks to docs vor 17 Jahren
nbd.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
nmi_watchdog.txt 1bb3a02907 x86: nmi_watchdog - documentation fix - v2 vor 17 Jahren
nommu-mmap.txt 930e652a21 [PATCH] NOMMU: Make futexes work under NOMMU conditions vor 18 Jahren
numastat.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
oops-tracing.txt 95b570c9ce Taint kernel after WARN_ON(condition) vor 17 Jahren
paride.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
parport-lowlevel.txt cdb32706f6 plip: fix parport_register_device name parameter vor 17 Jahren
parport.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
pi-futex.txt 96016cfae5 fix a typo in Documentation/pi-futex.txt vor 18 Jahren
pnp.txt b1c7192df1 Documentation: Replace obsolete "driverfs" with "sysfs". vor 17 Jahren
preempt-locking.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
prio_tree.txt 670e9f34ee Documentation: remove duplicated words vor 18 Jahren
ramdisk.txt fac8b209b1 Remove final traces of long-deprecated "ramdisk" kernel parm vor 17 Jahren
rbtree.txt c742b53114 [PATCH] Documentation/rbtree.txt vor 18 Jahren
rfkill.txt dac24ab396 [RFKILL]: Add rfkill documentation vor 17 Jahren
riscom8.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
robust-futex-ABI.txt 4ae0edc21b Fix typos in /Documentation : 'U-Z' vor 18 Jahren
robust-futexes.txt 5d3f083d8f Fix typos in /Documentation : Misc vor 18 Jahren
rocket.txt 53cb47268e Fix typos in Documentation/: 'S' vor 18 Jahren
rt-mutex-design.txt 9ba0bdfd04 [PATCH] typo fixes for rt-mutex-design.txt vor 18 Jahren
rt-mutex.txt a6537be932 [PATCH] pi-futex: rt mutex docs vor 19 Jahren
rtc.txt 8696e70267 rtc: cleanup example code vor 17 Jahren
serial-console.txt f1a1c2dc2a [PATCH] doc: more serial-console info vor 19 Jahren
sgi-ioc4.txt 22329b511a [PATCH] ioc4: Core driver rewrite vor 20 Jahren
sgi-visws.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
sparse.txt a55028ff74 [PATCH] update 'getting sparse' info. vor 18 Jahren
specialix.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
spinlocks.txt 14dadf1d5e Add additional examples in Documentation/spinlocks.txt vor 17 Jahren
stable_api_nonsense.txt a2765e81d8 stable_api_nonsense.txt: Disambiguate the use of "this" by using "that" to refer to the syscall interface vor 18 Jahren
stable_kernel_rules.txt 46cdf871d9 stable_kernel_rules: fix must already be in mainline vor 17 Jahren
stallion.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
svga.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
sx.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
sysfs-rules.txt 30b1b28001 Fix Doc/sysfs-rules typos vor 18 Jahren
sysrq.txt 5045bcae0f sysrq: add show-backtrace-on-all-cpus function vor 17 Jahren
tty.txt 3ac40b9b5e termios: document callback more clearly vor 17 Jahren
unaligned-memory-access.txt e8d49f3a6f Fix typos in Documentation/unaligned-memory-access.txt vor 17 Jahren
unicode.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
unshare.txt 670e9f34ee Documentation: remove duplicated words vor 18 Jahren
video-output.txt b03637b886 output: Add output class document vor 18 Jahren
volatile-considered-harmful.txt 0faa454802 "volatile considered harmful" vor 18 Jahren
voyager.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren
zorro.txt 1da177e4c3 Linux-2.6.12-rc2 vor 20 Jahren

README.DAC960

Linux Driver for Mylex DAC960/AcceleRAID/eXtremeRAID PCI RAID Controllers

Version 2.2.11 for Linux 2.2.19
Version 2.4.11 for Linux 2.4.12

PRODUCTION RELEASE

11 October 2001

Leonard N. Zubkoff
Dandelion Digital
lnz@dandelion.com

Copyright 1998-2001 by Leonard N. Zubkoff


INTRODUCTION

Mylex, Inc. designs and manufactures a variety of high performance PCI RAID
controllers. Mylex Corporation is located at 34551 Ardenwood Blvd., Fremont,
California 94555, USA and can be reached at 510.796.6100 or on the World Wide
Web at http://www.mylex.com. Mylex Technical Support can be reached by
electronic mail at mylexsup@us.ibm.com, by voice at 510.608.2400, or by FAX at
510.745.7715. Contact information for offices in Europe and Japan is available
on their Web site.

The latest information on Linux support for DAC960 PCI RAID Controllers, as
well as the most recent release of this driver, will always be available from
my Linux Home Page at URL "http://www.dandelion.com/Linux/". The Linux DAC960
driver supports all current Mylex PCI RAID controllers including the new
eXtremeRAID 2000/3000 and AcceleRAID 352/170/160 models which have an entirely
new firmware interface from the older eXtremeRAID 1100, AcceleRAID 150/200/250,
and DAC960PJ/PG/PU/PD/PL. See below for a complete controller list as well as
minimum firmware version requirements. For simplicity, in most places this
documentation refers to DAC960 generically rather than explicitly listing all
the supported models.

Driver bug reports should be sent via electronic mail to "lnz@dandelion.com".
Please include with the bug report the complete configuration messages reported
by the driver at startup, along with any subsequent system messages relevant to
the controller's operation, and a detailed description of your system's
hardware configuration. Driver bugs are actually quite rare; if you encounter
problems with disks being marked offline, for example, please contact Mylex
Technical Support as the problem is related to the hardware configuration
rather than the Linux driver.

Please consult the RAID controller documentation for detailed information
regarding installation and configuration of the controllers. This document
primarily provides information specific to the Linux support.


DRIVER FEATURES

The DAC960 RAID controllers are supported solely as high performance RAID
controllers, not as interfaces to arbitrary SCSI devices. The Linux DAC960
driver operates at the block device level, the same level as the SCSI and IDE
drivers. Unlike other RAID controllers currently supported on Linux, the
DAC960 driver is not dependent on the SCSI subsystem, and hence avoids all the
complexity and unnecessary code that would be associated with an implementation
as a SCSI driver. The DAC960 driver is designed for as high a performance as
possible with no compromises or extra code for compatibility with lower
performance devices. The DAC960 driver includes extensive error logging and
online configuration management capabilities. Except for initial configuration
of the controller and adding new disk drives, most everything can be handled
from Linux while the system is operational.

The DAC960 driver is architected to support up to 8 controllers per system.
Each DAC960 parallel SCSI controller can support up to 15 disk drives per
channel, for a maximum of 60 drives on a four channel controller; the fibre
channel eXtremeRAID 3000 controller supports up to 125 disk drives per loop for
a total of 250 drives. The drives installed on a controller are divided into
one or more "Drive Groups", and then each Drive Group is subdivided further
into 1 to 32 "Logical Drives". Each Logical Drive has a specific RAID Level
and caching policy associated with it, and it appears to Linux as a single
block device. Logical Drives are further subdivided into up to 7 partitions
through the normal Linux and PC disk partitioning schemes. Logical Drives are
also known as "System Drives", and Drive Groups are also called "Packs". Both
terms are in use in the Mylex documentation; I have chosen to standardize on
the more generic "Logical Drive" and "Drive Group".

DAC960 RAID disk devices are named in the style of the obsolete Device File
System (DEVFS). The device corresponding to Logical Drive D on Controller C
is referred to as /dev/rd/cCdD, and the partitions are called /dev/rd/cCdDp1
through /dev/rd/cCdDp7. For example, partition 3 of Logical Drive 5 on
Controller 2 is referred to as /dev/rd/c2d5p3. Note that unlike with SCSI
disks the device names will not change in the event of a disk drive failure.
The DAC960 driver is assigned major numbers 48 - 55 with one major number per
controller. The 8 bits of minor number are divided into 5 bits for the Logical
Drive and 3 bits for the partition.


SUPPORTED DAC960/AcceleRAID/eXtremeRAID PCI RAID CONTROLLERS

The following list comprises the supported DAC960, AcceleRAID, and eXtremeRAID
PCI RAID Controllers as of the date of this document. It is recommended that
anyone purchasing a Mylex PCI RAID Controller not in the following table
contact the author beforehand to verify that it is or will be supported.

eXtremeRAID 3000
1 Wide Ultra-2/LVD SCSI channel
2 External Fibre FC-AL channels
233MHz StrongARM SA 110 Processor
64 Bit 33MHz PCI (backward compatible with 32 Bit PCI slots)
32MB/64MB ECC SDRAM Memory

eXtremeRAID 2000
4 Wide Ultra-160 LVD SCSI channels
233MHz StrongARM SA 110 Processor
64 Bit 33MHz PCI (backward compatible with 32 Bit PCI slots)
32MB/64MB ECC SDRAM Memory

AcceleRAID 352
2 Wide Ultra-160 LVD SCSI channels
100MHz Intel i960RN RISC Processor
64 Bit 33MHz PCI (backward compatible with 32 Bit PCI slots)
32MB/64MB ECC SDRAM Memory

AcceleRAID 170
1 Wide Ultra-160 LVD SCSI channel
100MHz Intel i960RM RISC Processor
16MB/32MB/64MB ECC SDRAM Memory

AcceleRAID 160 (AcceleRAID 170LP)
1 Wide Ultra-160 LVD SCSI channel
100MHz Intel i960RS RISC Processor
Built in 16M ECC SDRAM Memory
PCI Low Profile Form Factor - fit for 2U height

eXtremeRAID 1100 (DAC1164P)
3 Wide Ultra-2/LVD SCSI channels
233MHz StrongARM SA 110 Processor
64 Bit 33MHz PCI (backward compatible with 32 Bit PCI slots)
16MB/32MB/64MB Parity SDRAM Memory with Battery Backup

AcceleRAID 250 (DAC960PTL1)
Uses onboard Symbios SCSI chips on certain motherboards
Also includes one onboard Wide Ultra-2/LVD SCSI Channel
66MHz Intel i960RD RISC Processor
4MB/8MB/16MB/32MB/64MB/128MB ECC EDO Memory

AcceleRAID 200 (DAC960PTL0)
Uses onboard Symbios SCSI chips on certain motherboards
Includes no onboard SCSI Channels
66MHz Intel i960RD RISC Processor
4MB/8MB/16MB/32MB/64MB/128MB ECC EDO Memory

AcceleRAID 150 (DAC960PRL)
Uses onboard Symbios SCSI chips on certain motherboards
Also includes one onboard Wide Ultra-2/LVD SCSI Channel
33MHz Intel i960RP RISC Processor
4MB Parity EDO Memory

DAC960PJ 1/2/3 Wide Ultra SCSI-3 Channels
66MHz Intel i960RD RISC Processor
4MB/8MB/16MB/32MB/64MB/128MB ECC EDO Memory

DAC960PG 1/2/3 Wide Ultra SCSI-3 Channels
33MHz Intel i960RP RISC Processor
4MB/8MB ECC EDO Memory

DAC960PU 1/2/3 Wide Ultra SCSI-3 Channels
Intel i960CF RISC Processor
4MB/8MB EDRAM or 2MB/4MB/8MB/16MB/32MB DRAM Memory

DAC960PD 1/2/3 Wide Fast SCSI-2 Channels
Intel i960CF RISC Processor
4MB/8MB EDRAM or 2MB/4MB/8MB/16MB/32MB DRAM Memory

DAC960PL 1/2/3 Wide Fast SCSI-2 Channels
Intel i960 RISC Processor
2MB/4MB/8MB/16MB/32MB DRAM Memory

DAC960P 1/2/3 Wide Fast SCSI-2 Channels
Intel i960 RISC Processor
2MB/4MB/8MB/16MB/32MB DRAM Memory

For the eXtremeRAID 2000/3000 and AcceleRAID 352/170/160, firmware version
6.00-01 or above is required.

For the eXtremeRAID 1100, firmware version 5.06-0-52 or above is required.

For the AcceleRAID 250, 200, and 150, firmware version 4.06-0-57 or above is
required.

For the DAC960PJ and DAC960PG, firmware version 4.06-0-00 or above is required.

For the DAC960PU, DAC960PD, DAC960PL, and DAC960P, either firmware version
3.51-0-04 or above is required (for dual Flash ROM controllers), or firmware
version 2.73-0-00 or above is required (for single Flash ROM controllers)

Please note that not all SCSI disk drives are suitable for use with DAC960
controllers, and only particular firmware versions of any given model may
actually function correctly. Similarly, not all motherboards have a BIOS that
properly initializes the AcceleRAID 250, AcceleRAID 200, AcceleRAID 150,
DAC960PJ, and DAC960PG because the Intel i960RD/RP is a multi-function device.
If in doubt, contact Mylex RAID Technical Support (mylexsup@us.ibm.com) to
verify compatibility. Mylex makes available a hard disk compatibility list at
http://www.mylex.com/support/hdcomp/hd-lists.html.


DRIVER INSTALLATION

This distribution was prepared for Linux kernel version 2.2.19 or 2.4.12.

To install the DAC960 RAID driver, you may use the following commands,
replacing "/usr/src" with wherever you keep your Linux kernel source tree:

cd /usr/src
tar -xvzf DAC960-2.2.11.tar.gz (or DAC960-2.4.11.tar.gz)
mv README.DAC960 linux/Documentation
mv DAC960.[ch] linux/drivers/block
patch -p0 < DAC960.patch (if DAC960.patch is included)
cd linux
make config
make bzImage (or zImage)

Then install "arch/i386/boot/bzImage" or "arch/i386/boot/zImage" as your
standard kernel, run lilo if appropriate, and reboot.

To create the necessary devices in /dev, the "make_rd" script included in
"DAC960-Utilities.tar.gz" from http://www.dandelion.com/Linux/ may be used.
LILO 21 and FDISK v2.9 include DAC960 support; also included in this archive
are patches to LILO 20 and FDISK v2.8 that add DAC960 support, along with
statically linked executables of LILO and FDISK. This modified version of LILO
will allow booting from a DAC960 controller and/or mounting the root file
system from a DAC960.

Red Hat Linux 6.0 and SuSE Linux 6.1 include support for Mylex PCI RAID
controllers. Installing directly onto a DAC960 may be problematic from other
Linux distributions until their installation utilities are updated.


INSTALLATION NOTES

Before installing Linux or adding DAC960 logical drives to an existing Linux
system, the controller must first be configured to provide one or more logical
drives using the BIOS Configuration Utility or DACCF. Please note that since
there are only at most 6 usable partitions on each logical drive, systems
requiring more partitions should subdivide a drive group into multiple logical
drives, each of which can have up to 6 usable partitions. Also, note that with
large disk arrays it is advisable to enable the 8GB BIOS Geometry (255/63)
rather than accepting the default 2GB BIOS Geometry (128/32); failing to so do
will cause the logical drive geometry to have more than 65535 cylinders which
will make it impossible for FDISK to be used properly. The 8GB BIOS Geometry
can be enabled by configuring the DAC960 BIOS, which is accessible via Alt-M
during the BIOS initialization sequence.

For maximum performance and the most efficient E2FSCK performance, it is
recommended that EXT2 file systems be built with a 4KB block size and 16 block
stride to match the DAC960 controller's 64KB default stripe size. The command
"mke2fs -b 4096 -R stride=16 " is appropriate. Unless there will be a
large number of small files on the file systems, it is also beneficial to add
the "-i 16384" option to increase the bytes per inode parameter thereby
reducing the file system metadata. Finally, on systems that will only be run
with Linux 2.2 or later kernels it is beneficial to enable sparse superblocks
with the "-s 1" option.


DAC960 ANNOUNCEMENTS MAILING LIST

The DAC960 Announcements Mailing List provides a forum for informing Linux
users of new driver releases and other announcements regarding Linux support
for DAC960 PCI RAID Controllers. To join the mailing list, send a message to
"dac960-announce-request@dandelion.com" with the line "subscribe" in the
message body.


CONTROLLER CONFIGURATION AND STATUS MONITORING

The DAC960 RAID controllers running firmware 4.06 or above include a Background
Initialization facility so that system downtime is minimized both for initial
installation and subsequent configuration of additional storage. The BIOS
Configuration Utility (accessible via Alt-R during the BIOS initialization
sequence) is used to quickly configure the controller, and then the logical
drives that have been created are available for immediate use even while they
are still being initialized by the controller. The primary need for online
configuration and status monitoring is then to avoid system downtime when disk
drives fail and must be replaced. Mylex's online monitoring and configuration
utilities are being ported to Linux and will become available at some point in
the future. Note that with a SAF-TE (SCSI Accessed Fault-Tolerant Enclosure)
enclosure, the controller is able to rebuild failed drives automatically as
soon as a drive replacement is made available.

The primary interfaces for controller configuration and status monitoring are
special files created in the /proc/rd/... hierarchy along with the normal
system console logging mechanism. Whenever the system is operating, the DAC960
driver queries each controller for status information every 10 seconds, and
checks for additional conditions every 60 seconds. The initial status of each
controller is always available for controller N in /proc/rd/cN/initial_status,
and the current status as of the last status monitoring query is available in
/proc/rd/cN/current_status. In addition, status changes are also logged by the
driver to the system console and will appear in the log files maintained by
syslog. The progress of asynchronous rebuild or consistency check operations
is also available in /proc/rd/cN/current_status, and progress messages are
logged to the system console at most every 60 seconds.

Starting with the 2.2.3/2.0.3 versions of the driver, the status information
available in /proc/rd/cN/initial_status and /proc/rd/cN/current_status has been
augmented to include the vendor, model, revision, and serial number (if
available) for each physical device found connected to the controller:

***** DAC960 RAID Driver Version 2.2.3 of 19 August 1999 *****
Copyright 1998-1999 by Leonard N. Zubkoff
Configuring Mylex DAC960PRL PCI RAID Controller
Firmware Version: 4.07-0-07, Channels: 1, Memory Size: 16MB
PCI Bus: 1, Device: 4, Function: 1, I/O Address: Unassigned
PCI Address: 0xFE300000 mapped at 0xA0800000, IRQ Channel: 21
Controller Queue Depth: 128, Maximum Blocks per Command: 128
Driver Queue Depth: 127, Maximum Scatter/Gather Segments: 33
Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
SAF-TE Enclosure Management Enabled
Physical Devices:
0:0 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 68016775HA
Disk Status: Online, 17928192 blocks
0:1 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 68004E53HA
Disk Status: Online, 17928192 blocks
0:2 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 13013935HA
Disk Status: Online, 17928192 blocks
0:3 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 13016897HA
Disk Status: Online, 17928192 blocks
0:4 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 68019905HA
Disk Status: Online, 17928192 blocks
0:5 Vendor: IBM Model: DRVS09D Revision: 0270
Serial Number: 68012753HA
Disk Status: Online, 17928192 blocks
0:6 Vendor: ESG-SHV Model: SCA HSBP M6 Revision: 0.61
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 89640960 blocks, Write Thru
No Rebuild or Consistency Check in Progress

To simplify the monitoring process for custom software, the special file
/proc/rd/status returns "OK" when all DAC960 controllers in the system are
operating normally and no failures have occurred, or "ALERT" if any logical
drives are offline or critical or any non-standby physical drives are dead.

Configuration commands for controller N are available via the special file
/proc/rd/cN/user_command. A human readable command can be written to this
special file to initiate a configuration operation, and the results of the
operation can then be read back from the special file in addition to being
logged to the system console. The shell command sequence

echo "" > /proc/rd/c0/user_command
cat /proc/rd/c0/user_command

is typically used to execute configuration commands. The configuration
commands are:

flush-cache

The "flush-cache" command flushes the controller's cache. The system
automatically flushes the cache at shutdown or if the driver module is
unloaded, so this command is only needed to be certain a write back cache
is flushed to disk before the system is powered off by a command to a UPS.
Note that the flush-cache command also stops an asynchronous rebuild or
consistency check, so it should not be used except when the system is being
halted.

kill :

The "kill" command marks the physical drive : as DEAD.
This command is provided primarily for testing, and should not be used
during normal system operation.

make-online :

The "make-online" command changes the physical drive :
from status DEAD to status ONLINE. In cases where multiple physical drives
have been killed simultaneously, this command may be used to bring all but
one of them back online, after which a rebuild to the final drive is
necessary.

Warning: make-online should only be used on a dead physical drive that is
an active part of a drive group, never on a standby drive. The command
should never be used on a dead drive that is part of a critical logical
drive; rebuild should be used if only a single drive is dead.

make-standby :

The "make-standby" command changes physical drive :
from status DEAD to status STANDBY. It should only be used in cases where
a dead drive was replaced after an automatic rebuild was performed onto a
standby drive. It cannot be used to add a standby drive to the controller
configuration if one was not created initially; the BIOS Configuration
Utility must be used for that currently.

rebuild :

The "rebuild" command initiates an asynchronous rebuild onto physical drive
:. It should only be used when a dead drive has been
replaced.

check-consistency

The "check-consistency" command initiates an asynchronous consistency check
of with automatic restoration. It can be used
whenever it is desired to verify the consistency of the redundancy
information.

cancel-rebuild
cancel-consistency-check

The "cancel-rebuild" and "cancel-consistency-check" commands cancel any
rebuild or consistency check operations previously initiated.


EXAMPLE I - DRIVE FAILURE WITHOUT A STANDBY DRIVE

The following annotated logs demonstrate the controller configuration and and
online status monitoring capabilities of the Linux DAC960 Driver. The test
configuration comprises 6 1GB Quantum Atlas I disk drives on two channels of a
DAC960PJ controller. The physical drives are configured into a single drive
group without a standby drive, and the drive group has been configured into two
logical drives, one RAID-5 and one RAID-6. Note that these logs are from an
earlier version of the driver and the messages have changed somewhat with newer
releases, but the functionality remains similar. First, here is the current
status of the RAID configuration:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
***** DAC960 RAID Driver Version 2.0.0 of 23 March 1999 *****
Copyright 1998-1999 by Leonard N. Zubkoff
Configuring Mylex DAC960PJ PCI RAID Controller
Firmware Version: 4.06-0-08, Channels: 3, Memory Size: 8MB
PCI Bus: 0, Device: 19, Function: 1, I/O Address: Unassigned
PCI Address: 0xFD4FC000 mapped at 0x8807000, IRQ Channel: 9
Controller Queue Depth: 128, Maximum Blocks per Command: 128
Driver Queue Depth: 127, Maximum Scatter/Gather Segments: 33
Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 5498880 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Online, 3305472 blocks, Write Thru
No Rebuild or Consistency Check in Progress

gwynedd:/u/lnz# cat /proc/rd/status
OK

The above messages indicate that everything is healthy, and /proc/rd/status
returns "OK" indicating that there are no problems with any DAC960 controller
in the system. For demonstration purposes, while I/O is active Physical Drive
1:1 is now disconnected, simulating a drive failure. The failure is noted by
the driver within 10 seconds of the controller's having detected it, and the
driver logs the following console status messages indicating that Logical
Drives 0 and 1 are now CRITICAL as a result of Physical Drive 1:1 being DEAD:

DAC960#0: Physical Drive 1:2 Error Log: Sense Key = 6, ASC = 29, ASCQ = 02
DAC960#0: Physical Drive 1:3 Error Log: Sense Key = 6, ASC = 29, ASCQ = 02
DAC960#0: Physical Drive 1:1 killed because of timeout on SCSI command
DAC960#0: Physical Drive 1:1 is now DEAD
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) is now CRITICAL
DAC960#0: Logical Drive 1 (/dev/rd/c0d1) is now CRITICAL

The Sense Keys logged here are just Check Condition / Unit Attention conditions
arising from a SCSI bus reset that is forced by the controller during its error
recovery procedures. Concurrently with the above, the driver status available
from /proc/rd also reflects the drive failure. The status message in
/proc/rd/status has changed from "OK" to "ALERT":

gwynedd:/u/lnz# cat /proc/rd/status
ALERT

and /proc/rd/c0/current_status has been updated:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Dead, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Critical, 5498880 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Critical, 3305472 blocks, Write Thru
No Rebuild or Consistency Check in Progress

Since there are no standby drives configured, the system can continue to access
the logical drives in a performance degraded mode until the failed drive is
replaced and a rebuild operation completed to restore the redundancy of the
logical drives. Once Physical Drive 1:1 is replaced with a properly
functioning drive, or if the physical drive was killed without having failed
(e.g., due to electrical problems on the SCSI bus), the user can instruct the
controller to initiate a rebuild operation onto the newly replaced drive:

gwynedd:/u/lnz# echo "rebuild 1:1" > /proc/rd/c0/user_command
gwynedd:/u/lnz# cat /proc/rd/c0/user_command
Rebuild of Physical Drive 1:1 Initiated

The echo command instructs the controller to initiate an asynchronous rebuild
operation onto Physical Drive 1:1, and the status message that results from the
operation is then available for reading from /proc/rd/c0/user_command, as well
as being logged to the console by the driver.

Within 10 seconds of this command the driver logs the initiation of the
asynchronous rebuild operation:

DAC960#0: Rebuild of Physical Drive 1:1 Initiated
DAC960#0: Physical Drive 1:1 Error Log: Sense Key = 6, ASC = 29, ASCQ = 01
DAC960#0: Physical Drive 1:1 is now WRITE-ONLY
DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 1% completed

and /proc/rd/c0/current_status is updated:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Write-Only, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Critical, 5498880 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Critical, 3305472 blocks, Write Thru
Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 6% completed

As the rebuild progresses, the current status in /proc/rd/c0/current_status is
updated every 10 seconds:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Write-Only, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Critical, 5498880 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Critical, 3305472 blocks, Write Thru
Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 15% completed

and every minute a progress message is logged to the console by the driver:

DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 32% completed
DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 63% completed
DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 94% completed
DAC960#0: Rebuild in Progress: Logical Drive 1 (/dev/rd/c0d1) 94% completed

Finally, the rebuild completes successfully. The driver logs the status of the
logical and physical drives and the rebuild completion:

DAC960#0: Rebuild Completed Successfully
DAC960#0: Physical Drive 1:1 is now ONLINE
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) is now ONLINE
DAC960#0: Logical Drive 1 (/dev/rd/c0d1) is now ONLINE

/proc/rd/c0/current_status is updated:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 5498880 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Online, 3305472 blocks, Write Thru
Rebuild Completed Successfully

and /proc/rd/status indicates that everything is healthy once again:

gwynedd:/u/lnz# cat /proc/rd/status
OK


EXAMPLE II - DRIVE FAILURE WITH A STANDBY DRIVE

The following annotated logs demonstrate the controller configuration and and
online status monitoring capabilities of the Linux DAC960 Driver. The test
configuration comprises 6 1GB Quantum Atlas I disk drives on two channels of a
DAC960PJ controller. The physical drives are configured into a single drive
group with a standby drive, and the drive group has been configured into two
logical drives, one RAID-5 and one RAID-6. Note that these logs are from an
earlier version of the driver and the messages have changed somewhat with newer
releases, but the functionality remains similar. First, here is the current
status of the RAID configuration:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
***** DAC960 RAID Driver Version 2.0.0 of 23 March 1999 *****
Copyright 1998-1999 by Leonard N. Zubkoff
Configuring Mylex DAC960PJ PCI RAID Controller
Firmware Version: 4.06-0-08, Channels: 3, Memory Size: 8MB
PCI Bus: 0, Device: 19, Function: 1, I/O Address: Unassigned
PCI Address: 0xFD4FC000 mapped at 0x8807000, IRQ Channel: 9
Controller Queue Depth: 128, Maximum Blocks per Command: 128
Driver Queue Depth: 127, Maximum Scatter/Gather Segments: 33
Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Online, 2201600 blocks
1:3 - Disk: Standby, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 4399104 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Online, 2754560 blocks, Write Thru
No Rebuild or Consistency Check in Progress

gwynedd:/u/lnz# cat /proc/rd/status
OK

The above messages indicate that everything is healthy, and /proc/rd/status
returns "OK" indicating that there are no problems with any DAC960 controller
in the system. For demonstration purposes, while I/O is active Physical Drive
1:2 is now disconnected, simulating a drive failure. The failure is noted by
the driver within 10 seconds of the controller's having detected it, and the
driver logs the following console status messages:

DAC960#0: Physical Drive 1:1 Error Log: Sense Key = 6, ASC = 29, ASCQ = 02
DAC960#0: Physical Drive 1:3 Error Log: Sense Key = 6, ASC = 29, ASCQ = 02
DAC960#0: Physical Drive 1:2 killed because of timeout on SCSI command
DAC960#0: Physical Drive 1:2 is now DEAD
DAC960#0: Physical Drive 1:2 killed because it was removed
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) is now CRITICAL
DAC960#0: Logical Drive 1 (/dev/rd/c0d1) is now CRITICAL

Since a standby drive is configured, the controller automatically begins
rebuilding onto the standby drive:

DAC960#0: Physical Drive 1:3 is now WRITE-ONLY
DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 4% completed

Concurrently with the above, the driver status available from /proc/rd also
reflects the drive failure and automatic rebuild. The status message in
/proc/rd/status has changed from "OK" to "ALERT":

gwynedd:/u/lnz# cat /proc/rd/status
ALERT

and /proc/rd/c0/current_status has been updated:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Dead, 2201600 blocks
1:3 - Disk: Write-Only, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Critical, 4399104 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Critical, 2754560 blocks, Write Thru
Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 4% completed

As the rebuild progresses, the current status in /proc/rd/c0/current_status is
updated every 10 seconds:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Dead, 2201600 blocks
1:3 - Disk: Write-Only, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Critical, 4399104 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Critical, 2754560 blocks, Write Thru
Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 40% completed

and every minute a progress message is logged on the console by the driver:

DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 40% completed
DAC960#0: Rebuild in Progress: Logical Drive 0 (/dev/rd/c0d0) 76% completed
DAC960#0: Rebuild in Progress: Logical Drive 1 (/dev/rd/c0d1) 66% completed
DAC960#0: Rebuild in Progress: Logical Drive 1 (/dev/rd/c0d1) 84% completed

Finally, the rebuild completes successfully. The driver logs the status of the
logical and physical drives and the rebuild completion:

DAC960#0: Rebuild Completed Successfully
DAC960#0: Physical Drive 1:3 is now ONLINE
DAC960#0: Logical Drive 0 (/dev/rd/c0d0) is now ONLINE
DAC960#0: Logical Drive 1 (/dev/rd/c0d1) is now ONLINE

/proc/rd/c0/current_status is updated:

***** DAC960 RAID Driver Version 2.0.0 of 23 March 1999 *****
Copyright 1998-1999 by Leonard N. Zubkoff
Configuring Mylex DAC960PJ PCI RAID Controller
Firmware Version: 4.06-0-08, Channels: 3, Memory Size: 8MB
PCI Bus: 0, Device: 19, Function: 1, I/O Address: Unassigned
PCI Address: 0xFD4FC000 mapped at 0x8807000, IRQ Channel: 9
Controller Queue Depth: 128, Maximum Blocks per Command: 128
Driver Queue Depth: 127, Maximum Scatter/Gather Segments: 33
Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Dead, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 4399104 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Online, 2754560 blocks, Write Thru
Rebuild Completed Successfully

and /proc/rd/status indicates that everything is healthy once again:

gwynedd:/u/lnz# cat /proc/rd/status
OK

Note that the absence of a viable standby drive does not create an "ALERT"
status. Once dead Physical Drive 1:2 has been replaced, the controller must be
told that this has occurred and that the newly replaced drive should become the
new standby drive:

gwynedd:/u/lnz# echo "make-standby 1:2" > /proc/rd/c0/user_command
gwynedd:/u/lnz# cat /proc/rd/c0/user_command
Make Standby of Physical Drive 1:2 Succeeded

The echo command instructs the controller to make Physical Drive 1:2 into a
standby drive, and the status message that results from the operation is then
available for reading from /proc/rd/c0/user_command, as well as being logged to
the console by the driver. Within 60 seconds of this command the driver logs:

DAC960#0: Physical Drive 1:2 Error Log: Sense Key = 6, ASC = 29, ASCQ = 01
DAC960#0: Physical Drive 1:2 is now STANDBY
DAC960#0: Make Standby of Physical Drive 1:2 Succeeded

and /proc/rd/c0/current_status is updated:

gwynedd:/u/lnz# cat /proc/rd/c0/current_status
...
Physical Devices:
0:1 - Disk: Online, 2201600 blocks
0:2 - Disk: Online, 2201600 blocks
0:3 - Disk: Online, 2201600 blocks
1:1 - Disk: Online, 2201600 blocks
1:2 - Disk: Standby, 2201600 blocks
1:3 - Disk: Online, 2201600 blocks
Logical Drives:
/dev/rd/c0d0: RAID-5, Online, 4399104 blocks, Write Thru
/dev/rd/c0d1: RAID-6, Online, 2754560 blocks, Write Thru
Rebuild Completed Successfully