From owner-freebsd-stable@FreeBSD.ORG Mon Oct 15 00:14:05 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1199F16A419; Mon, 15 Oct 2007 00:14:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id A924A13C455; Mon, 15 Oct 2007 00:14:04 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l9F0DvlP062319; Sun, 14 Oct 2007 18:13:58 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4712B0A6.1050408@samsco.org> Date: Sun, 14 Oct 2007 18:13:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Jan Mikkelsen References: <008801c80e65$47cbe650$639049d9@EC1a> <4712A494.30803@samsco.org> <000a01c80ebb$49227f90$db677eb0$@com> In-Reply-To: <000a01c80ebb$49227f90$db677eb0$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Sun, 14 Oct 2007 18:13:58 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-stable@freebsd.org, 'Ivan Voras' , freebsd-geom@freebsd.org Subject: Re: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 00:14:05 -0000 Jan Mikkelsen wrote: > Scott Long wrote: >> Ivan Voras wrote: >>> Either that or file system errors. Does fsck run ok or does >> it say >>> anything unusual? >>> >> No, filesystem corruption has nothing to do with g_vfs_done >> messages. > > Well, perhaps not directly but I think filesystem corruption can > indirectly cause g_vfs_done messages. > > If a filesystem is corrupt, the filesystem might attempt to read an > out-of-range block, leading to a g_vfs_done error. This was the > case for some of the arcmsr problems last year. > > In this case, I think the original poster said that the block > number was out of range for the device. > > Regards, > > Jan Mikkelsen > > Yeah, you're right, the block number is absurd, and it could well be caused by a bad block pointer in the filesystem. It sounds like he's getting this problem even on fresh installs, which ordinarily would point to a bad driver. If it's happening with both TWA and ATA, it's hard to blame both of those drivers. Scott