From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 09:01:27 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7575D16A41C for ; Fri, 10 Jun 2005 09:01:27 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1775943D48 for ; Fri, 10 Jun 2005 09:01:26 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 6605860F5; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 53A1F60F2; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 2DA0B33C3B; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) To: "Darren Pilgrim" References: <000001c56d93$8b65c590$0a2a15ac@SMILEY> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 10 Jun 2005 11:01:20 +0200 In-Reply-To: <000001c56d93$8b65c590$0a2a15ac@SMILEY> (Darren Pilgrim's message of "Fri, 10 Jun 2005 01:08:10 -0700") Message-ID: <86k6l2y49r.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Learn: ham X-Spam-Score: -5.1/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-hackers@freebsd.org Subject: Re: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 09:01:27 -0000 "Darren Pilgrim" writes: > So yeah I gueuss my fob is busted or funky. The CAM errors are "just" the > drive saying there's no media present, so maybe the device doesn't support > the commands necessary to report disk capacity? Is there a way to educate > CAM about this so the attach procedure doesn't break? It's a direct-access storage device. It *can't* not support the READ CAPACITY command. > Why would the CAM errors prevent GEOM from creating the MBR geom during > attach but not when trying to mount /dev/da0? My guess is that the fob is marginal and takes a while to stabilize after being plugged in. GEOM first tastes it when it is plugged in, it is still funky, and GEOM fails to read the partition table. Then you try to mount /dev/da0, it is opened r/w, which causes GEOM to retaste it once it is closed; by that time, it has settled and the second tasting succeeds. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no