Date: Thu, 17 Nov 2011 12:45:22 -0500 From: Douglas Gilbert <dgilbert@interlog.com> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: scsi@freebsd.org Subject: Re: smartd blows away mfi config Message-ID: <4EC54832.60101@interlog.com> In-Reply-To: <86zkfuoefv.fsf@ds4.des.no> References: <86d3cqpxh0.fsf@ds4.des.no> <4EC538BF.8060804@interlog.com> <86zkfuoefv.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11-11-17 12:18 PM, Dag-Erling Smørgrav wrote: > Douglas Gilbert<dgilbert@interlog.com> writes: >> Not sure how SES devices appear as device nodes (i.e. /dev entries) >> in FreeBSD. If they can be mistaken for disks then smartd has >> a problem which I will look into. > > Thanks. > > As a quick fix, how do I write a drivedb entry that tells smartd to stay > away from it? As far as I know, smartmontools' drivedb only applies to ATA disks. So I don't think that it comes into the picture for SCSI devices. The "Peripheral Device Type" in a SCSI INQUIRY response is the appropriate field to filter on. Doug Gilbert > I find it strange that nobody else has run into this yet... perhaps > it's specific to a particular firmware version. > > DES
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC54832.60101>