<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Thanks for the reply, Alex. </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">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: </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><div id="bloop_customfont" style="margin: 0px;">setprop temp-multiple </div><div id="bloop_customfont" style="margin: 0px;">setprop selftest-multiple </div><div id="bloop_customfont" style="margin: 0px;">setprop smart-multiple</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">but no granular control for specific devices. </div><div id="bloop_customfont" style="margin: 0px;"><br></div></div> <div id="bloop_sign_1392920777335651840" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Anh Quach<br>Sent with Airmail</div></div> <br><p style="color:#A0A0A8;">On February 19, 2014 at 8:04:20 PM, Alex Wilson (<a href="mailto://alex@cooperi.net">alex@cooperi.net</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>
<title></title>
<div>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).</div>
<div><br></div>
<div>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.</div>
<div><br></div>
<div>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...</div>
<div><br></div>
<div><br></div>
<br>
<div>
<div>On 19 Feb 2014, at 10:17 am, Anh Quach <<a href="mailto:anhquach@me.com">anhquach@me.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; margin: 0px;">Is
it possible to tell the disk-transport FMA module to ignore
over-temperature on only a certain set of disks? </div>
<div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; margin: 0px;">
<br></div>
<div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; margin: 0px;">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. </div>
<div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; margin: 0px;">
<br></div>
<div id="bloop_customfont" style="font-family: Helvetica, Arial; font-size: 13px; margin: 0px;">
Thanks in advance!</div>
<br>
<div id="bloop_sign_1392767560475051776" class="bloop_sign">
<div style="font-family: helvetica, arial; font-size: 13px;">
-- <br>
Anh Quach<br>
Sent with Airmail</div>
</div>
_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a></div>
</blockquote>
</div>
<br>
_______________________________________________
<br>OmniOS-discuss mailing list
<br>OmniOS-discuss@lists.omniti.com
<br>http://lists.omniti.com/mailman/listinfo/omnios-discuss
<br></div></div></span></blockquote></body></html>