From owner-freebsd-current Wed Dec 11 11:45:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95C6837B401 for ; Wed, 11 Dec 2002 11:45:23 -0800 (PST) Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23DFA43EB2 for ; Wed, 11 Dec 2002 11:45:23 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (eq.net [208.186.104.163]) by delivery.infowest.com (Postfix) with ESMTP id B7870E3A87B; Wed, 11 Dec 2002 12:45:09 -0700 (MST) Message-ID: <3DF795C1.8050905@infowest.com> Date: Wed, 11 Dec 2002 12:45:05 -0700 From: "Aaron D. Gifford" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Cc: Greg 'groggy' Lehey Subject: Re: HELP: vinum and newfs on 5.0-RC1 References: <3DF509E5.9050706@infowest.com> <063E4372-0BDE-11D7-BAE8-00039380DD2C@uky.edu> <20021210012955.GK1952@wantadilla.lemis.com> <3DF5458B.2010809@infowest.com> <20021210014211.GO1952@wantadilla.lemis.com> In-Reply-To: <20021210014211.GO1952@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I wrote in my previous message: > ># newfs -O 2 -U /dev/vinum/raid5vol >newfs: /dev/vinum/raid5vol: 'e' partition is unavailable > ... >Here's my vinum setup: ... > volume raid5vol Let me correct this to state that the full volume name was "raid5volume" and I just shortened it to save typing. This turns out to be important. Looking at newfs.c, it looks like the last letter of the special device is used to choose the partition. Thus "e" was selected during my attempts to do newfs. (Note to self: Do NOT to abbreviate when reporting trouble.) Today I renamed my vinum volume as "sp1a", and newfs worked just fine: #newfs -U -O 2 /dev/vinum/sp1a A few attempts to use disklabel on /dev/vinum/sp1a still had some problems (i.e. any changes made during 'disklabel -e /dev/vinum/sp1a' were still ignored as subsequent disklabel sessions would revert to the version I saw before my changes - 'disklabel -e -r /dev/vinum/sp1a' did save my changes to the on-disk--or on vinum volume in this case--label but the in-memory label remaind unchanged), but apparently I didn't really need to use disklabel with this newly named volume. So... Is there some place in the vinum manual that I missed that discusses volume naming requirements that had I read I could have avoided this trouble? Thanks! Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message