From owner-freebsd-current@FreeBSD.ORG Thu Jul 15 22:55:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C9A16A4CE for ; Thu, 15 Jul 2004 22:55:52 +0000 (GMT) Received: from av7-1-sn4.m-sp.skanova.net (av7-1-sn4.m-sp.skanova.net [81.228.10.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B5BD43D2F for ; Thu, 15 Jul 2004 22:55:52 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id 6CD8237F0D; Fri, 16 Jul 2004 00:55:51 +0200 (CEST) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av7-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 5DD9937E42 for ; Fri, 16 Jul 2004 00:55:51 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 44E5D37E42 for ; Fri, 16 Jul 2004 00:55:51 +0200 (CEST) From: "Daniel Eriksson" To: Date: Fri, 16 Jul 2004 00:55:44 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Subject: vinum dangling vnode & GEOM stripe problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2004 22:55:52 -0000 Background: I have a machine running a fairly recent CURRENT (2004.07.12.22.00.00) = that has a bunch of discs. 26 discs are hooked up through the onboard ATA and SATA controllers (VIA KT-600), an Adaptec 29160 and two HighPoint = RocketRAID 454 (4 channel HPT374 cards). The discs are used either as single discs = or combined into RAID-0 and RAID-1 arrays using the "old" vinum or ataraid. There's 11 different physical file systems at this point, plus over 200 mount_nullfs rw mounts. I'm having some hardware problems relating to interrupt routing, but the last kernel (see above) seems pretty stable. = I still get interrupt storms during device probing every now and then = though, which worries me, but after tweaking the interrupt storm threshold (hw.intr_storm_threshold=3D5000) this seems to be less of a problem. Problem #1: I usually boot the machine single-user so that I can verify all discs = were detected during boot (interrupt storms sometime prevent proper probing, forcing ataraid and/or vinum to mark arrays as crashed). However, after = the latest kernel upgrade and the threshold tweaking the machine has been = stable enough that I dared to try a normal multi-user boot. However, it always = ends up with a vinum panic (dangling vnode, as reported by others). = Unfortunately I don't have enough swap for a coredump right now so I cannot provide = any additional info (hope to change that in the next couple of days). Problem #2: Yesterday I was playing around with the GEOM stripe module, and it = messed the machine up pretty bad when trying to create a simple 2 disc stripe. = It made all the discs that were attached to ataraid arrays time out, which resulted in the stripes getting crashed, and then it eventually panicked = in some vfs function. As soon as I have added more swap I'll post a more detailed error = report. Just wanted to throw this out as it seems to be very easy for me to reproduce the panics. Since the machine is rather sensitive to downtime = I usually go into panic mode myself when it crash, so I'll blame the lack = of details on that. Once I get the kernel to save coredumps it should be = easier to provide accurate info (kernel already compiled with debug symbols and KDB/DDB). /Daniel Eriksson