From owner-freebsd-stable Fri Sep 20 6:16:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502E637B401; Fri, 20 Sep 2002 06:16:43 -0700 (PDT) Received: from mail.thinkburst.com (juno.geocomm.com [204.214.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE5E143E42; Fri, 20 Sep 2002 06:16:42 -0700 (PDT) (envelope-from jbozza@thinkburst.com) Received: from mailgate.thinkburstmedia.com (gateway.thinkburstmedia.com [204.214.64.100]) by mail.thinkburst.com (Postfix) with ESMTP id 210F1367C2; Fri, 20 Sep 2002 08:17:03 -0500 (CDT) Received: from sigma.geocomm.com (sigma.geocomm.com [10.1.1.5]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id B53F220F03; Fri, 20 Sep 2002 08:16:41 -0500 (CDT) Received: by sigma.geocomm.com (Postfix, from userid 805) id A787D24544; Fri, 20 Sep 2002 08:16:41 -0500 (CDT) Received: from bozza (dhcp00.geocomm.com [10.1.1.100]) by sigma.geocomm.com (Postfix) with ESMTP id 3CF7A2453E; Fri, 20 Sep 2002 08:16:41 -0500 (CDT) From: "Jaime Bozza" To: "'Greg 'groggy' Lehey'" Cc: Subject: RE: vinum ad0h/ad0s1h issue Date: Fri, 20 Sep 2002 08:13:44 -0500 Message-ID: <009201c260a7$8c356670$6401010a@bozza> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20020919051420.GH37454@wantadilla.lemis.com> Importance: Normal X-Sanitizer: ThinkBurst Media, Inc. mail filter Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I think I now understand the problem here. Try the following patch >and tell me if it solves the problem: > >--- vinumio.c 2 May 2002 08:43:44 -0000 1.52.2.6 >+++ vinumio.c 19 Sep 2002 05:10:27 -0000 Tried patch. System no longer reads ad0h/ad2h, but after the second 'vinum start', the system shows 0 drives ('vinum ld' lists nothing.) The third 'vinum start' reads ad0s1h/ad2s1h again. Additional starts cycle between the two (no drives, correct drives.) >The problem here is that vinum_scandisk() tries to read from each >slice. If it doesn't find any (for example, on a dedicated disk), it >tries the compatibility slice. That normally works fine, but if all >of the slices have already been read, it still falls through into this >part. Removing it should solve your problem; the real solution is a >little more complicated and involves recognizing that we already know >this drive. I probably won't do that until I finally have the root >file system running on Vinum, which will require mods in this same >area. Understandable. Personally, now that I know the issue I just make sure that I unload vinum if I'm not going to reboot after doing work in single-user mode. It's not like I'm constantly having to jump back into single-user. BTW, regarding my original problem with the filesystem corruption, it hasn't returned. I'm going to figure it was some combination of softupdates/ata-wc that caused the filesystems to be out of sync. Thanks! Jaime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message