From owner-freebsd-stable Wed Sep 18 11:49: 1 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 1AD1137B401; Wed, 18 Sep 2002 11:49:00 -0700 (PDT) Received: from mail.thinkburst.com (juno.geocomm.com [204.214.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65E1D43E65; Wed, 18 Sep 2002 11:48:59 -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 5E562A95E; Wed, 18 Sep 2002 13:49:24 -0500 (CDT) Received: from sigma.geocomm.com (sigma.geocomm.com [10.1.1.5]) by mailgate.thinkburstmedia.com (Postfix) with ESMTP id 5E5A420F03; Wed, 18 Sep 2002 13:48:58 -0500 (CDT) Received: by sigma.geocomm.com (Postfix, from userid 805) id 5443C24543; Wed, 18 Sep 2002 13:48:58 -0500 (CDT) Received: from bozza (dhcp00.geocomm.com [10.1.1.100]) by sigma.geocomm.com (Postfix) with ESMTP id DC81624542; Wed, 18 Sep 2002 13:48:57 -0500 (CDT) From: "Jaime Bozza" To: Cc: "'Greg 'groggy' Lehey'" Subject: vinum ad0h/ad0s1h issue Date: Wed, 18 Sep 2002 13:46:06 -0500 Message-ID: <025001c25f43$a57fd120$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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <15612.59696.734708.21623@horsey.gshapiro.net> 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 Recently I wrote a message regarding some filesystem problems. One of the differences I noticed on the system was that my drives were referencing ad0/2h instead of ad0/2s1h. I also stated that rebooting solved the problem. I was just able to duplicate the problem. Here's what I found out. (Happens on a recent 4.7-RC, vinum configuration with start_vinum="YES") First, boot into single-user mode. Next, mount / (for rw), then run 'vinum start'. Vinum reads the data from ad0s1h/ad2s1h correctly. (I had then run my fsck's and such on the drives when I had the problem) Exit the single-user shell (which starts booting into multiuser) /etc/rc and friends run 'vinum start' a second time, which causes the system to read data from ad0h/ad2h. System seems to be fine except for "vinum ld". When rebooting the system and letting it come up normally, it reads the slices correctly. If I run "vinum stop" before exiting single-user mode, it works fine. In fact, I can easily duplicate the error just by running "vinum start" twice. (BTW, a third time will panic the system and cause vinum to read the ad0h/ad2h on reboot) You said it was a known problem. How difficult would it be to ingore subsequent start's (The overall start kind) once vinum has already been "started", or could there be a situation where you'd want to start it more than once? (I can't think of any) Jaime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message