From owner-freebsd-fs@FreeBSD.ORG Thu Jul 3 20:37:56 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4169DDC for ; Thu, 3 Jul 2014 20:37:56 +0000 (UTC) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BA6F4223B for ; Thu, 3 Jul 2014 20:37:56 +0000 (UTC) Received: from spa-sysadm-01.spa.umn.edu ([134.84.199.8]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1X2nEA-000DSu-F3 for freebsd-fs@freebsd.org; Thu, 03 Jul 2014 15:03:31 -0500 Message-ID: <53B5B712.5050404@physics.umn.edu> Date: Thu, 03 Jul 2014 15:03:30 -0500 From: Graham Allan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: FreeBSD Filesystems Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mrmachenry.spa.umn.edu X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 Subject: replaced da devices not being detected X-SA-Exim-Version: 4.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2014 20:37:57 -0000 Running a FreeBSD 9.1 server with four attached Supermicro SAS JBODs, 45 drives in each. Sometimes when we replace a drive due to failure, the new drive isn't detected. At that point we can swap the drive in and out or between vacant slots with nothing appearing in dmesg or other logs. But we know the drive is working because it is detected by the chassis if queried with sg3utils. No effect from "camcontrol rescan" etc, either. Rebooting the server does result in the drive being detected but obviously this isn't a desirable way to fix it. It does seem to me like we get to replace some number of drives without incident, then after some point no new da devices are detected. Just wondering if anyone has seen this, or if there are any sysctls which might affect it or other ways to tickle the system into behaving as expected. Thanks for any advice, Graham -- ------------------------------------------------------------------------- Graham Allan School of Physics and Astronomy - University of Minnesota -------------------------------------------------------------------------