From owner-freebsd-geom@FreeBSD.ORG Sun Oct 14 13:35:03 2007 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BE4D16A41A; Sun, 14 Oct 2007 13:35:03 +0000 (UTC) (envelope-from d_elbracht@ecngs.de) Received: from ecngs.de (mail.ecngs.de [217.73.144.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2F5A013C459; Sun, 14 Oct 2007 13:35:02 +0000 (UTC) (envelope-from d_elbracht@ecngs.de) Received: from EC1a (ec1.elbracht.net [217.73.144.99]) by ecngs.de (SurgeMail 3.8f2) with ESMTP id 1773130-1922481 for multiple; Sun, 14 Oct 2007 15:22:59 +0200 From: "d_elbracht" To: , Date: Sun, 14 Oct 2007 15:22:32 +0200 Message-ID: <008801c80e65$47cbe650$639049d9@EC1a> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcgOZUbPq0zqvOG2QwSFpRt2OPaAhw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: Subject: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Oct 2007 13:35:03 -0000 we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of 2007-10-09 Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron 2216, da3 is on a 3ware 9550-12 we are seeing this error: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 on a 12 GB Hyperdrive the offset changes sometimes, but it is always 81064794xxxxxxxxx and well out the 12GB range. We did have the Hyperdrive connected directly to the mainboards SATA0 (ad4) with similar errors. We used to have a md instead of the hyperdrive before, coming up with similar errors. Blocksize on the partition is 8192 (newsfs -b 8192 ..). We did have a blocksize of 65536 before, but after some hours (sometimes days), the machine will be unresponsible with "newbuf" as a waitmessage in top and has to be hard-reset. Regarding "newbuf", as well as nbufkv and nbufbs, I will write a seperate message to the list. According to systat -vm, da3 does tps > 500 (yes, that's a lot) This leads to an assumption, the error has to do with very high IOs per second on a SMP machine. The system-disk is a RAID1 on an ICP 5805. All other disks (51) are 20 gstripe'd partitions. Any hint to diagnose / fix the problem is well appreciated. Cheers, Dieter