From owner-freebsd-stable Sun Jan 27 16:57:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 85CC437B416; Sun, 27 Jan 2002 16:57:20 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id g0S0vJv75536; Mon, 28 Jan 2002 01:57:19 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 28 Jan 2002 01:57:17 +0100 (CET) From: Martin Blapp To: Greg Lehey Cc: Bernd Walter , Subject: Re: double fault with vinum and 4.5 RC3 In-Reply-To: <20020128105227.A18585@wantadilla.lemis.com> Message-ID: <20020128014332.W68322-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Hi Greg, > So it seems. I've heard of this in a couple of cases. It would be > interesting to see the log output, but if I understand you correctly > you have since found a way to work around the problem. I suspect that > there was something in the disk label which confused the issue, but it > would be nice to find what it is. Possibly /dev/da1e would have > worked. I tried first with /dev/da1e. Then I shought I should use /dev/da1s1e. No way. Errm, If it's allowed to ask, what is exactly the difference between the name with slice (s1e) and just the slice entry (e) ? I suppose I know what happened. da1 still had the vinum information stored at the same place as before from my three mirrors I made before. One time it worked, but vinum showed me a size of 1024m, exactly the size what /var was before. You see, da0s1e is exactly at the same place as the da0s1g with the new config ! I just did: - Removed the three slices da0s1e, da0s1f, da0s1g. - Removed the three slices da1s1e, da1s1f, da1s1g. - Made a big partiton on them. - Executed newfs on it. - Relabeled this partition as type "vinum" - Executed vinum create config and had the failure. Should be easy to find out what vinum does wrong here. Btw: I have a crash dump available for the race you said, it you are interested. If you login to the machine, there are also the log entries in /var/log/messages. Another thing I noted: newfs seems to make less superblock backups on big volumes now. Vinum still does make as many backups as FreeBSD did earlier for other filesystems. At least my experiments lead to some bug discovery ;) Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message