Re: automatic fsck on gmirror failure

2008-02-22 Thread Wojciech Puchar
$ grep -i fsck /etc/defaults/rc.conf fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. gmirror(8) / geom(8) should automatically remove (degrade) components with bad I/O operations after a certain threshold, but I'm pretty sure it doesn't. yes it does

Re: automatic fsck on gmirror failure

2008-02-22 Thread Brian A. Seklecki
On Sun, 2008-02-03 at 23:39 +0100, Wojciech Puchar wrote: it failed while rebuilding with badly written data on the disk that was used, while other rebuild. now it can't read it. if you are sure that it doesn't pass through fsck before second reboot, do the following. 1) turn off

Re: automatic fsck on gmirror failure

2008-02-22 Thread Wojciech Puchar
gmirror(8) / geom(8) should automatically remove (degrade) components with bad I/O operations after a certain threshold, but I'm pretty sure it doesn't. but i'm absolutely sure it does because it did several times for me ___

Re: automatic fsck on gmirror failure

2008-02-22 Thread Brian A. Seklecki
On Fri, 22 Feb 2008, Wojciech Puchar wrote: $ grep -i fsck /etc/defaults/rc.conf fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. gmirror(8) / geom(8) should automatically remove (degrade) components with bad I/O operations after a certain threshold, but I'm

Re: automatic fsck on gmirror failure

2008-02-22 Thread Brian A. Seklecki
On Fri, 22 Feb 2008, Wojciech Puchar wrote: gmirror(8) / geom(8) should automatically remove (degrade) components with bad I/O operations after a certain threshold, but I'm pretty sure it doesn't. but i'm absolutely sure it does because it did several times for me Finally I had some time

Re: automatic fsck on gmirror failure

2008-02-03 Thread Wojciech Puchar
it failed while rebuilding with badly written data on the disk that was used, while other rebuild. now it can't read it. if you are sure that it doesn't pass through fsck before second reboot, do the following. 1) turn off gmirror 2) clear gmirror header on both providers 3) run fsck the