From owner-freebsd-questions@FreeBSD.ORG Tue Dec 7 00:41:52 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D63216A4CE for ; Tue, 7 Dec 2004 00:41:52 +0000 (GMT) Received: from rrzmta1.rz.uni-regensburg.de (rrzmta1.rz.uni-regensburg.de [132.199.1.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0744043D2D for ; Tue, 7 Dec 2004 00:41:52 +0000 (GMT) (envelope-from markus.hoenicka@mhoenicka.de) Received: from rrzmta1.rz.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 19FA312711B for ; Tue, 7 Dec 2004 01:44:49 +0100 (CET) Received: from tipi.mininet (rrzras2-87.rz.uni-regensburg.de [132.199.209.87]) by rrzmta1.rz.uni-regensburg.de (Postfix) with ESMTP id 2D6D8126FA5 for ; Tue, 7 Dec 2004 01:44:47 +0100 (CET) X-Mailer: emacs 21.2.1 (via feedmail 8 Q); VM 7.03 under Emacs 21.2.1 From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16820.57579.721193.800699@tipi.mininet> Date: Mon, 6 Dec 2004 23:44:59 +0100 To: freebsd-questions In-Reply-To: <20041206023125.GU92212@wantadilla.lemis.com> References: <16819.48747.223694.368063@tipi.mininet> <20041206023125.GU92212@wantadilla.lemis.com> Subject: Re: vinum raid5: newfs throws an error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 00:41:52 -0000 Greg 'groggy' Lehey writes: > There was once an error in the stripe size calculations that meant > that there were holes in the plexes. Maybe it's still there (old > Vinum is not being maintained). But you should have seen that in the > console messages at create time. > > > Vinum reports the disk sizes as 17500MB (da1) and 17359MB (da2, > > da3). The raid5 volume and plex have a size of 33GB. > > This looks like the kind of scenario where that could happen. Try > this: > > 1. First, find a better stripe size. It shouldn't be a power of 2, > but it should be a multiple of 16 kB. I'd recommend 496 kB. This > won't fix the problem, but it's something you should do anyway > > 2. Calculate the length of an exact number of stripes, and create the > subdisks in that length. Try again and see what happens. > > 3. Use gvinum instead of vinum and try both ways. > Ok, I decreased the stripe size to 496, regardless of whether it has anything to do with my problem. Next I set the subdisk length to 17359m on all disks, and things started to work ok. No more newfs errors here. Before doing this I also had a brief encounter with gvinum. There is no manpage in 5.3BETA7, so I assumed it groks the same config files as vinum. However, this did not do me any good as it simply rebooted the box. I guess gvinum works better in RELEASE. Thanks a lot for your help. Markus -- Markus Hoenicka markus.hoenicka@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de