From owner-freebsd-stable@FreeBSD.ORG Mon Oct 15 00:04:57 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 3996C16A46D for ; Mon, 15 Oct 2007 00:04:57 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 2752513C481 for ; Mon, 15 Oct 2007 00:04:55 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 90463 invoked from network); 14 Oct 2007 23:38:35 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 14 Oct 2007 23:38:35 -0000 Received: (qmail 20180 invoked by uid 907); 14 Oct 2007 23:38:12 -0000 Received: from [192.168.1.51] (HELO janmxp) (192.168.1.51) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Mon, 15 Oct 2007 09:38:12 +1000 From: "Jan Mikkelsen" To: "'Scott Long'" , "'Ivan Voras'" References: <008801c80e65$47cbe650$639049d9@EC1a> <4712A494.30803@samsco.org> In-Reply-To: <4712A494.30803@samsco.org> Date: Mon, 15 Oct 2007 09:38:12 +1000 Organization: Transactionware Message-ID: <000a01c80ebb$49227f90$db677eb0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgOuTwXgPkltFJRQheLCsRVqNf9bwAAU00w Content-Language: en-au Cc: freebsd-stable@freebsd.org, 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:04:57 -0000 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