# [OmniOS-discuss] Granular control of fma modules

Anh Quach anhquach at me.com
Thu Feb 20 19:03:38 UTC 2014

- Previous message: [OmniOS-discuss] Granular control of fma modules
- Next message: [OmniOS-discuss] Granular control of fma modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Thanks for the reply, Alex.

    Yeah, to my knowledge fmadm acquit seems to just clear the one unique event. From a “for your own good” standpoint, it makes sense that one probably shouldn’t be disabling this kind of stuff, but I’m surprised the .conf has no way of filtering by SMART data. Looks like you can set these properties:

    setprop temp-multiple
    setprop selftest-multiple
    setprop smart-multiple

    but no granular control for specific devices.

    --
    Anh Quach
    Sent with Airmail

    On February 19, 2014 at 8:04:20 PM, Alex Wilson (alex at cooperi.net) wrote:

    I’ve been recently trying to find a way to get disk-transport to ignore certain SMART values when deciding if a disk is going to fail — in particular, the Seek Error figures, which Seagate drives tend to make out to be a lot more significant than they really are, using a different scale to everyone else. I had a look through the code for disk-transport though and it doesn’t seem like it can do very much to help: the module itself is pretty dumb and just passes on errors from deeper down in the libraries it uses (where there is also no means of filtering out events).

    The closest you can get is to use “fmadm acquit”, but it doesn’t seem to work for me — it clears out the fault that’s there for the moment, but doesn’t block it from coming back again, even though the man page suggests that it should. I guess this is because of disk-transport generating new UUIDs for each individual event rather than on the type of event? It’s a bit annoying.

    I’d really like a disk-transport.conf var to say “ignore this particular type of SMART data” or “ignore it for these disks”. Maybe I should sit down and try to write some code for it...

    On 19 Feb 2014, at 10:17 am, Anh Quach <anhquach at me.com> wrote:

    Is it possible to tell the disk-transport FMA module to ignore over-temperature on only a certain set of disks?

    I’m doing testing with some Seagate Constellation.3’s that seem to run hotter even at idle than the rest of my disks (39-44 C) and they are continually getting flagged for over temp. I know I can disable to the temp alert for that module but I don’t want to disable it for all disks, just these new Seagates.

    Thanks in advance!

    --
    Anh Quach
    Sent with Airmail
    _______________________________________________
    OmniOS-discuss mailing list
    OmniOS-discuss at lists.omniti.com
    http://lists.omniti.com/mailman/listinfo/omnios-discuss

    _______________________________________________
    OmniOS-discuss mailing list
    OmniOS-discuss at lists.omniti.com
    http://lists.omniti.com/mailman/listinfo/omnios-discuss
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20140220/d4750be5/attachment.html>

- Previous message: [OmniOS-discuss] Granular control of fma modules
- Next message: [OmniOS-discuss] Granular control of fma modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list