Contributed by jolan on from the 3.8-goodies dept.
Some of you may remember that shortly before the 3.7 release was finalized, the Adaptec RAID driver was disabled in GENERIC. This was done to reinforce OpenBSD's "because it has to be free" philosophy after getting the run around from Adaptec about when freely available RAID management tools would become available. In the spirit of displacing proprietary tools by creating a free and open competitor, OpenBSD 3.8 will ship with the beginnings of a RAID management framework.
Work initially began by making the ami(4) driver aware of the mappings of physical disks to logical disks and adding RAID ioctls. Next, support for SCSI enclosures was fleshed out. The safte(4) driver was written and the ses(4) driver was re-written. This was done for the reporting of hardware monitor data such as temperature, fan speed, and power status. It also provided functionality for blinking lights on the enclosure so finding the correct drive to swap would be easier. Finally, the bioctl(8) utility was designed in order to query drive status, enable alarms, and issue commands on a given RAID controller.
This is a minimal implementation which lacks a drive failure notification mechanism (bioctl must be run to see a failure), but there is support for hot spares and online rebuilding of a degraded array. Keep in mind that bio(4) and bioctl are the start of framework which can be expanded to support more hardware.
Theo has sent a mail to misc@ with more information and a mini-demo of how all the pieces and commands fit together.
(Comments are closed)
By Rene (203.45.43.241) on
Comments
By Anonymous Coward (204.209.209.129) on
By Anonymous Coward (12.33.122.68) on
By Chris (24.76.100.162) on
By Jim (68.250.26.213) on
Comments
By Brad (216.138.195.228) brad at comstyle dot com on
Comments
By Michael Knudsen (217.157.199.114) on
I want cac(4) and mpt(4) as well. I guess in general the chance is pretty slim of getting anything else supported -- at least from what I've heard about vendors' willingness to open up documentation.
Comments
By Marco Peereboom (67.64.89.177) marco@peereboom.us on www.peereboom.us
By Jim (68.250.26.213) on
Or does that bloat the install script too much?.?.
Comments
By Nate (65.94.50.71) on
Comments
By Brad (216.138.195.228) brad at comstyle dot com on
By David Gwynne (130.102.78.195) loki@animata.net on
Comments
By Anonymous Coward (12.33.122.68) on
Comments
By David Gwynne (220.245.180.132) loki@animata.net on
Comments
By chris cappuccio (198.175.14.5) on
Comments
By Brad (216.138.195.228) on
By Anonymous Coward (80.90.29.7) on