From owner-freebsd-questions@FreeBSD.ORG Fri Mar 26 16:10:37 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 2BD5716A4CE; Fri, 26 Mar 2004 16:10:37 -0800 (PST) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAD0843D39; Fri, 26 Mar 2004 16:10:36 -0800 (PST) (envelope-from sellis@d216-232-192-244.bchsia.telus.net) Received: from d216-232-192-244.bchsia.telus.net ([216.232.192.244]) by priv-edtnes46.telusplanet.netESMTP <20040327001035.GNRC26972.priv-edtnes46.telusplanet.net@d216-232-192-244.bchsia.telus.net>; Fri, 26 Mar 2004 17:10:35 -0700 Received: from d216-232-192-244.bchsia.telus.net (localhost [127.0.0.1]) i2R0AYI2046408; Fri, 26 Mar 2004 16:11:00 -0800 (PST) (envelope-from sellis@d216-232-192-244.bchsia.telus.net) Received: (from sellis@localhost)i2R0AO5p046407; Fri, 26 Mar 2004 16:10:24 -0800 (PST) (envelope-from sellis) Date: Fri, 26 Mar 2004 16:10:13 -0800 From: Sean Ellis To: "Greg 'groggy' Lehey" Message-ID: <20040327001013.GC45524@telus.net> Mail-Followup-To: Greg 'groggy' Lehey , freebsd-questions@freebsd.org References: <20040326191245.GA45524@telus.net> <20040326233018.GD31700@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040326233018.GD31700@wantadilla.lemis.com> User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: vinum list anomaly X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: sellis@telus.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2004 00:10:37 -0000 On Sat, Mar 27, 2004 at 10:00:18AM +1030, Greg 'groggy' Lehey wrote: > On Friday, 26 March 2004 at 11:12:45 -0800, Sean Ellis wrote: > > after adding too drives as a concatenated vinum volume I see a line in > > the `vinum list` output which doesn't look right to me. Specifically, the > > line that refers to spanned_log.p0.s0. Is there a typical explanation for > > something like this? > > > > 2 drives: > > D a State: up Device /dev/ad2s1e Avail: > > 10/4110 MB (0%) > > D b State: up Device /dev/ad3s1e Avail: > > 10/4110 MB (0%) > > This looks like your MUA folded it. It should look like this: > > > 2 drives: > > D a State: up Device /dev/ad2s1e Avail: 10/4110 MB (0%) > > D b State: up Device /dev/ad3s1e Avail: 10/4110 MB (0%) Sorry, the pasted in details did lose their formatting. The line that I'm curious about though appears below; the line referring to spanned_log.p0.s0. The two disks are identical, and I thought that I'd prepared them in like fashion, yet one displays "0 B Size" and the other "4100 MB Size". > > S spanned_log.p0.s0 State: up PO: 0 B Size: 4100 MB > > S spanned_log.p0.s1 State: up PO: 4100 MB Size: 4100 MB I've just ran `vinum list` again, and I now have other problems (below), so I will be dealing with them and seeing how things stand at that point. new 'list' S spanned_log.p0.s0 State: up PO: 0 B Size: 4100 MB S spanned_log.p0.s1 State: crashed PO: 4100 MB Size: 4100 MB -- Sean