From owner-freebsd-fs Tue Nov 12 5:41: 8 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 9F43137B401 for ; Tue, 12 Nov 2002 05:41:07 -0800 (PST) Received: from server3.fastmail.fm (server3.fastmail.fm [209.61.187.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 205EA43E6E for ; Tue, 12 Nov 2002 05:41:07 -0800 (PST) (envelope-from wohl@chessclub.com) Received: from server3.fastmail.fm (localhost [127.0.0.1]) by fastmail.fm (Postfix) with ESMTP id 536DB2FD5D; Tue, 12 Nov 2002 07:41:03 -0600 (CST) Received: from 127.0.0.1 ([127.0.0.1] helo=server3.fastmail.fm) by fastmail.fm with SMTP; Tue, 12 Nov 2002 07:41:03 -0600 Received: by server3.fastmail.fm (Postfix, from userid 99) id 49BA02FD55; Tue, 12 Nov 2002 07:41:03 -0600 (CST) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.2 (F2.6; T1.001; A1.48; B2.12; Q2.03) From: "Aaron Wohl" To: freebsd-fs@FreeBSD.ORG Date: Tue, 12 Nov 2002 07:41:03 -0600 X-Epoch: 1037108463 X-Sasl-enc: ozoPM9teTigDZf3q3Ml3gw Subject: 4.7 using current vinum to snapshot? Message-Id: <20021112134103.49BA02FD55@server3.fastmail.fm> 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 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message