From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 14 17:16:41 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0541916A4CE for ; Thu, 14 Apr 2005 17:16:41 +0000 (GMT) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0AFC43D41 for ; Thu, 14 Apr 2005 17:16:40 +0000 (GMT) (envelope-from mhersant@comcast.net) Received: from [192.168.2.102] (c-24-22-136-36.hsd1.wa.comcast.net[24.22.136.36]) by comcast.net (rwcrmhc14) with ESMTP id <2005041417164001400hn5j0e>; Thu, 14 Apr 2005 17:16:40 +0000 Message-ID: <425EA581.6080509@comcast.net> Date: Thu, 14 Apr 2005 10:16:49 -0700 From: Matt User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <425E913C.50502@comcast.net> <20050414161050.GO48482@cicely12.cicely.de> <425E9DD4.308@comcast.net> In-Reply-To: <425E9DD4.308@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: vinum question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 17:16:41 -0000 Matt wrote: > Bernd Walter wrote: > >> On Thu, Apr 14, 2005 at 08:50:20AM -0700, Matt wrote: >> >> >>> I have a two disk array that I want to move to another machine. It >>> is configured with striping using vinum. What is the best way to >>> set it up under a new machine? Should I simply load the old >>> vinum.conf file and enable vinum? Thanks much for any help. >>> >>> drive disk1 device /dev/ad5s1d >>> drive disk2 device /dev/ad6s1d >>> volume stripe >>> plex org striped 256k >>> sd length 114470m drive disk1 >>> sd length 114470m drive disk2 >>> >> >> >> Vinum should find and use the existing configuration. >> >> >> > Well, it hasn't been that easy. The new machine is running 5.3. At > boot I receive: > > panic: umount: dangling vnode > / /when vinum loads at boot. I get around this by starting vinum from > rc.local. The vinum device node (named stripe in this case) isn't in > /dev/vinum. Do I need to create it on the new machine. I placed the > old config file in /etc/vinum.conf. Is vinum supposed to create the > nodes automatically? Thanks much. > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > tmodel# vinum list 2 drives: D disk2 State: up /dev/ad6s1d A: 114470/114470 MB (100%) D disk1 State: up /dev/ad5s1d A: 114470/114470 MB (100%) 0 volumes: 0 plexes: 0 subdisks: Do I need to recreate the volumes? Vinum can't seem to find them. Hmmm.