From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 17 17:45:31 2011 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C051A106564A for ; Thu, 17 Nov 2011 17:45:31 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC628FC1D for ; Thu, 17 Nov 2011 17:45:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id CB2BB2041B5; Thu, 17 Nov 2011 18:45:27 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fuNITCx12djA; Thu, 17 Nov 2011 18:45:25 +0100 (CET) Received: from [192.168.48.66] (ip-17.55.99.216.dsl-cust.ca.inter.net [216.99.55.17]) by smtp.infotech.no (Postfix) with ESMTPA id 04B572041B3; Thu, 17 Nov 2011 18:45:24 +0100 (CET) Message-ID: <4EC54832.60101@interlog.com> Date: Thu, 17 Nov 2011 12:45:22 -0500 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <86d3cqpxh0.fsf@ds4.des.no> <4EC538BF.8060804@interlog.com> <86zkfuoefv.fsf@ds4.des.no> In-Reply-To: <86zkfuoefv.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: scsi@freebsd.org Subject: Re: smartd blows away mfi config X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2011 17:45:31 -0000 On 11-11-17 12:18 PM, Dag-Erling Smørgrav wrote: > Douglas Gilbert 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