Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD

On Friday 13 July 2007 11:48:19 am Constantine A. Murenin wrote:
On 12/07/2007 14:04, John Baldwin wrote:

On Thursday 12 July 2007 03:00:08 am Alexander Leidinger wrote:

Quoting John Baldwin <jhb@xxxxxxxxxxx> (from Wed, 11 Jul 2007

11:45:26 -0400):

On Wednesday 11 July 2007 07:49:59 am Alexander Leidinger wrote:

On the other hand you don't want to allow an userland tool to directly
mess around with the registers on your RAID or NIC to get some status...

Err, that's how all the RAID utilities I've used work. They send
firmware
commands from userland and parse the replies in userland. One exception

I've

That's sad... they should provide this functionality in the driver
instead, it would allow to use access restrictions for some parts.


Not really, it avoids having to duplicate a lot of work in drivers that
can be
written once in a cross-platform userland utility. Drivers aren't really
the
place to be monitoring raid status sending pages, e-mails, etc. It's best
to
let userland invoke sendmail, not the kernel. :)

John, I'm sorry to disappoint you, but RAID drivers in OpenBSD don't
implement SMTP and don't do emails, they only provide updates to the
sensors framework when there are some changes in the state of the drive. :)

sensorsd(8) is used to send alerts and emails based on the information
from the sensors framework, and user configuration.

bioctl(8) is used to configure RAID for _all drivers_. There are no
separate utilities for RAID configuration based on brand-name, just like
nowadays there are no separate utilities for configuring Ethernet
adapters. [0]

According to the various manpages on www.openbsd.org you cannot configure
arrays on the OS for at least mfi(4), ciss(4), twe(4), mpi(4) (like mpt(4) in
FreeBSD) or ami(4) (like amr(4) in FreeBSD). You can only do monitoring via
hw.sensors for ciss(4) and ami(4), and the example for monitoring ami(4) in
the manpage shows that you can only get volume level data, and as a _string_
and that you can't get backing physical drive status to know which physical
drive has failed and needs to be replaced:

$ sysctl hw.sensors.ami0
hw.sensors.ami0.drive0=online (sd0), OK
hw.sensors.ami0.drive1=degraded (sd1), WARNING
hw.sensors.ami0.drive2=failed (sd2), CRITICAL

--
John Baldwin
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Cloning a Windows Xp single hard drive to RAID 0 array
    ... hard drive to RAID configuration by using Acronis True Image software. ... This article is silent on the matter of getting RAID and SCSI drivers ... thats a windows configuration question, ...
    (freebsd-questions)
  • Re: Oracle 10gR2 / RAID-5 / SAN
    ... configuration issues, etc.  There used to be a bunch of papers about ... for critical files that do better in other RAID configurations, ... suggest that RAID 1 is the ideal disk configuration since ... has a dedicated controller that is singly tasked with handling all ...
    (comp.databases.oracle.server)
  • Installer fails for software RAID
    ... I've been unable to produce a working software RAID ... installer using a pretty standard configuration. ... Waiting for root file system... ... machine install. ...
    (Ubuntu)
  • Re: Need help installing OS6 on Dell PowerEdge 2600 with PERC4/Di RAID
    ... The above recommends setting both channels to RAID. ... been with channel 1 set to RAID and channel 2 set to SCSI. ... SCO on the "proper" configuration. ... in the driver package description. ...
    (comp.unix.sco.misc)
  • Re: new dell, dumb operator needs help!
    ... hard disks that are not in a raid configuration. ... listed under 'hard disk'. ... drives in 'my computer' then it is pretty clear that you do not have raid ...
    (alt.sys.pc-clone.dell)