From owner-freebsd-stable Wed Mar 18 16:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28830 for freebsd-stable-outgoing; Wed, 18 Mar 1998 16:03:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28822 for ; Wed, 18 Mar 1998 16:03:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA23639; Wed, 18 Mar 1998 15:59:56 -0800 (PST) Message-Id: <199803182359.PAA23639@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Wackerbarth cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: Disk layout concernes (was Re: ATTENTION: Call for opinion re: root device naming change ) In-reply-to: Your message of "Wed, 18 Mar 1998 17:08:02 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 15:59:53 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > At 4:32 PM -0600 3/18/98, Mike Smith wrote: > >The information so far is a good start; it's a disk configured with > >'disklabel auto'. > > As I recall, you had previously mentioned that to be the case which > was giving you trouble. That's correct; it was. There was a major shortcoming in the test cases due to an (incorrect) understanding on my part. This left a number of people (yourself included) severely inconvenienced, which I deeply regret. > > Now, how about the failure mode? What version of kern/vfs_conf.c are > >you using? > > Well, it's too late to tell... > While I was waiting for your reply, I did another update. > kern/vfs_conf.c got changed in the process. I suspect that means that > my latest attempt did not have your latest change. Ah. Does the new code work? The change in question was implemented a few days ago; I let it sit in -current for a few before that to make sure that it wasn't going to burn people again. > > How old is the bootblock on the disk? > How do I easily tell? You don't, unfortunately. Updating the bootblock is something you do explicitly; normally it's laid down when you label the disk the first time and never changed. In retrospect, if you used 'disklabel auto' on the disk in the first place, the bootblock is more than adequately new. > Sorry, I don't recall seeing that message. Obviously, if you hadn't updated in response to it. I tried to make sure I notified everyone that was having problems, but the usual "if it works, everyone is quiet" response seems prevalent. (Or I missed everyone. 8( ) > >Thanks for the response. > > And thanks for speaking up again. I'd prefer that we not need to back out > the changes. There are some strong arguments in both directions. If your system(s) are working correctly now, there are only a couple of minor issues and one remaining plaintiff to resolve before I am happy that we handle everything as well now as we ever have. > I'll let you know just as soon I I get a new kernel to try. Please do, and thanks for persisting. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message