mirror without destroying existing contents

2007-03-13 Thread Steve Franks
Anyone made a mirror w/o destroying what's in the disk already? The atacontrol man page is less than adequate in this respect...is is even possible? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-

Re: mirror without destroying existing contents

2007-03-13 Thread Chuck Swiger
On Mar 13, 2007, at 12:12 PM, Steve Franks wrote: Anyone made a mirror w/o destroying what's in the disk already? The atacontrol man page is less than adequate in this respect...is is even possible? Oh, yes-- it's certainly possible to create a mirror with live data, but one is advised to be

Re: mirror without destroying existing contents

2007-03-13 Thread John Nielsen
On Tuesday 13 March 2007 15:12, Steve Franks wrote: > Anyone made a mirror w/o destroying what's in the disk already? The > atacontrol man page is less than adequate in this respect...is is even > possible? If you want to use gmirror (which I recommend), the most conservative approach is as foll

Re: mirror without destroying existing contents

2007-03-13 Thread David Robillard
Anyone made a mirror w/o destroying what's in the disk already? The atacontrol man page is less than adequate in this respect...is is even possible? Oh, yes-- it's certainly possible to create a mirror with live data, but one is advised to be cautious and have a full backup available in case of

Re: mirror without destroying existing contents

2007-03-16 Thread Steve Franks
I get the following: #gmirror label -v -b split -s 1024 data ad0 can't store metadata on ad0: operation not permitted. Ideas? Same behavior with /dev/ad0. Does this only work with da0 disks, not sata drives? I'm logged in as root, not su. The drive is on a promise non-raid sata card (the sw

Re: mirror without destroying existing contents

2007-03-16 Thread John Nielsen
On Friday 16 March 2007 11:18, Steve Franks wrote: > I get the following: > > #gmirror label -v -b split -s 1024 data ad0 > can't store metadata on ad0: operation not permitted. That most likely means that you currently have a filesystem on ad0 mounted. If that's the case you should be glad that

Re: mirror without destroying existing contents

2007-03-16 Thread Steve Franks
On 3/16/07, John Nielsen <[EMAIL PROTECTED]> wrote: On Friday 16 March 2007 11:18, Steve Franks wrote: > I get the following: > > #gmirror label -v -b split -s 1024 data ad0 > can't store metadata on ad0: operation not permitted. That most likely means that you currently have a filesystem on ad0

Re: mirror without destroying existing contents

2007-03-16 Thread John Nielsen
On Friday 16 March 2007 15:48, Steve Franks wrote: > On 3/16/07, John Nielsen <[EMAIL PROTECTED]> wrote: > > On Friday 16 March 2007 11:18, Steve Franks wrote: > > > I get the following: > > > > > > #gmirror label -v -b split -s 1024 data ad0 > > > can't store metadata on ad0: operation not permitt

Re: mirror without destroying existing contents

2007-03-17 Thread Jonathan McKeown
On Friday 16 March 2007 21:48, Steve Franks wrote: > On 3/16/07, John Nielsen <[EMAIL PROTECTED]> wrote: > > On Friday 16 March 2007 11:18, Steve Franks wrote: > > > I get the following: > > > > > > #gmirror label -v -b split -s 1024 data ad0 > > > can't store metadata on ad0: operation not permitt

negative free blocks after mirror! [was: Re: mirror without destroying existing contents]

2007-03-19 Thread Steve Franks
On 3/17/07, Jonathan McKeown <[EMAIL PROTECTED]> wrote: On Friday 16 March 2007 21:48, Steve Franks wrote: > On 3/16/07, John Nielsen <[EMAIL PROTECTED]> wrote: > > On Friday 16 March 2007 11:18, Steve Franks wrote: > > > I get the following: > > > > > > #gmirror label -v -b split -s 1024 data ad

Re: negative free blocks after mirror! [was: Re: mirror without destroying existing contents]

2007-03-19 Thread John Nielsen
On Monday 19 March 2007 10:46, Steve Franks wrote: > Yes, the origonal disk was pretty full, but, I suspect this is not a good > thing: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0s1a507630 9525437176620%/ > devfs