Date: Wed, 18 Sep 2002 13:46:06 -0500 From: "Jaime Bozza" <jbozza@thinkburst.com> To: <freebsd-stable@FreeBSD.ORG> Cc: "'Greg 'groggy' Lehey'" <grog@FreeBSD.org> Subject: vinum ad0h/ad0s1h issue Message-ID: <025001c25f43$a57fd120$6401010a@bozza> In-Reply-To: <15612.59696.734708.21623@horsey.gshapiro.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?025001c25f43$a57fd120$6401010a>