From owner-freebsd-fs@FreeBSD.ORG Mon Aug 10 21:08:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F75B1065689 for ; Mon, 10 Aug 2009 21:08:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3F3A08FC3D for ; Mon, 10 Aug 2009 21:08:04 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D1C1146B09; Mon, 10 Aug 2009 17:08:03 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 2DF7C8A0AB; Mon, 10 Aug 2009 17:08:03 -0400 (EDT) From: John Baldwin To: "Hearn, Trevor" Date: Mon, 10 Aug 2009 17:07:49 -0400 User-Agent: KMail/1.9.7 References: <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34C3@ITS-HCWNEM03.ds.Vanderbilt.edu> <200908101605.12332.jhb@freebsd.org> <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34CC@ITS-HCWNEM03.ds.Vanderbilt.edu> In-Reply-To: <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34CC@ITS-HCWNEM03.ds.Vanderbilt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908101707.49526.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 10 Aug 2009 17:08:03 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: "freebsd-fs@freebsd.org" Subject: Re: UFS Filesystem issues, and the loss of my hair... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 21:08:04 -0000 On Monday 10 August 2009 4:15:44 pm Hearn, Trevor wrote: > Here is the chunk that I grabbed from the screen to save as a memento. :) > > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX last message repeated 20 times > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=1638d)]error = 5 > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX last message repeated 18 times > Aug 10 10:53:43 XXXX kernel: g_vfs_done()-da1p7[READ(offset= > Aug 10 10:53:43 XXXX kernel: -6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX last message repeated 19 times > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, l=ngth=16384)]error 1 5 > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX last message repeated 6 times > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384o]error = 5 > Aug 10 10:53:43 XXXX kernel: > Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:43 XXXX last message repeated 22 times > Aug 10 10:53:44 XXXX kernel: READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:44 XXXX kernel: g_vfs_done():da1p7[READ(offset=-6419569950008350720, length=16384)]error = 5 > Aug 10 10:53:44 XXXX last message repeated 849 times > > As you can see, it's a little disjointed. I would assume that the screwed up length information is from the speed at which it was coming out, and possibly another message got throw in at the same time? Yes, it does seem like it was part of one of the other messages. The isp(4) driver was just recently updated in HEAD by mjacob@ who has maintained that driver in the past. He may have some insight if there is an isp(4)-specific problem. -- John Baldwin