From owner-freebsd-fs Tue Nov 12 18:36:49 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 183C837B401 for ; Tue, 12 Nov 2002 18:36:48 -0800 (PST) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id B669943E6E for ; Tue, 12 Nov 2002 18:36:46 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id A21B5518FF; Wed, 13 Nov 2002 13:06:44 +1030 (CST) Date: Wed, 13 Nov 2002 13:06:44 +1030 From: Greg 'groggy' Lehey To: Aaron Wohl Cc: freebsd-fs@FreeBSD.ORG Subject: Re: 4.7 using current vinum to snapshot? Message-ID: <20021113023644.GC2919@wantadilla.lemis.com> References: <20021112134103.49BA02FD55@server3.fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021112134103.49BA02FD55@server3.fastmail.fm> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tuesday, 12 November 2002 at 7:41:03 -0600, Aaron Wohl wrote: > I am trying to use the current vinum in the stable release to do > snapshoting. I setup a raid 1 let the added drive sync, stop the added > drive, hook it up to a different volume, fsck it, mount it read only. > > It does work but I get a couple of error messages along the way. Is > anyone else using vinum to do snapshoting? Is there some other order to > do these steps in and not get the error messages? Im aware of the notes > in the vinum documentation about future directions for snapshoting... > > ## starting here the two disks are setup as mirror 1 > ## break the mirror and then mount the copy else where so it can be > backeed up > vinum detach cplex > vinum setstate down cplex > vinum setstate down cplex.s0 > # ignore error Can't attach cplex to mir2: 1 in next step it works > anyway > vinum attach cplex mir2 > fsck -y /dev/vinum/mir2 > mount /dev/vinum/mir2 /mnt2 > > ... backup /mnt2 > > ## put the disk back into the mirror > umount /dev/vinum/mir2 > vinum stop mir2 > vinum detach cplex > vinum setstate obsolete cplex.s0 > #ignore error 1 in next line > vinum attach cplex mirx > vinum start cplex.s0 It's very difficult to follow this description, especially since you ignore the error messages. Could you please take a look at the man page or the web site and send the information asked for there. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message