Re: gmirror: replacing failed disks

2005-01-19 Thread Christian Hiris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 19 January 2005 22:53, you wrote: > On Wed, Jan 19, 2005 at 06:55:53AM +0100, Christian Hiris wrote: [...] > > > > 2.2. Blank out gmirror metadata on ad4 > > # dd if=/dev/zero of=/dev/ad4 bs=512 skip=156301400 > > This command took

Re: gmirror: replacing failed disks

2005-01-19 Thread Doug Poland
On Wed, Jan 19, 2005 at 06:55:53AM +0100, Christian Hiris wrote: > > > GEOM_MIRROR[2]: Metadata on ad6 updated. Jan 18 21:07:17 sgwww02 kernel: > > GEOM_MIRROR[1]: Disk ad6 (device gm0s1) marked as dirty. Jan 18 21:07:17 > > sgwww02 kernel: GEOM_MIRROR[2]: Metadata on ad6 updated. > > > > and on a

Re: gmirror: replacing failed disks

2005-01-18 Thread Christian Hiris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 19 January 2005 05:36, Doug Poland wrote: > On Tue, Jan 18, 2005 at 09:02:48AM -0600, Doug Poland wrote: > > >> GEOM_MIRROR: Component ad4 (device gm0s1) broken, skipping. > > >> GEOM_MIRROR: Cannot add disk ad4 to gm0s1 (error=22). > > >

Re: gmirror: replacing failed disks

2005-01-18 Thread Doug Poland
On Tue, Jan 18, 2005 at 09:02:48AM -0600, Doug Poland wrote: > > >> GEOM_MIRROR: Component ad4 (device gm0s1) broken, skipping. > >> GEOM_MIRROR: Cannot add disk ad4 to gm0s1 (error=22). > > > > You can set 'kern.geom.mirror.debug=2' in /boot/loader.conf. This > > tells you more about what happens

Re: gmirror: replacing failed disks

2005-01-18 Thread Doug Poland
>> GEOM_MIRROR: Component ad4 (device gm0s1) broken, skipping. >> GEOM_MIRROR: Cannot add disk ad4 to gm0s1 (error=22). > > You can set 'kern.geom.mirror.debug=2' in /boot/loader.conf. This > tells you more about what happens. I tested all this at a very early > stage of development, so gmirror's

Re: gmirror: replacing failed disks

2005-01-17 Thread Doug Poland
On Sun, Jan 16, 2005 at 11:14:48PM +0100, Christian Hiris wrote: > On Sunday 16 January 2005 21:14, Doug Poland wrote: > > > > (My system has a provider gm0s1 with ad4 and ad6 as consumers, so > > I'll use those device names) > > > > Simulate ad4 failing: > > > > pull the drive > > put the drive ba

Re: gmirror: replacing failed disks

2005-01-16 Thread Christian Hiris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 16 January 2005 21:14, Doug Poland wrote: > Hello, > > I've got a bootable gmirror running on identical SATA drives on > 5.3-STABLE. The technique I've used to build the gmirror can be found > on http://people.freebsd.org/~rse/gmirror, under