Date: Fri, 22 Feb 2008 11:43:52 -0500 From: "Brian A. Seklecki" <lavalamp@spiritual-machines.org> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: Gunther Mayer <gunther.mayer@googlemail.com>, questions@freebsd.org Subject: Re: automatic fsck on gmirror failure Message-ID: <1203698632.10391.130.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> In-Reply-To: <20080203233311.X7800@wojtek.tensor.gdynia.pl> References: <47A6287C.9040902@gmail.com> <20080203233311.X7800@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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 gmirror > > 2) clear gmirror header on both providers > > 3) run fsck the other drive (not ad6, but the other used on mirror). > Also don't forget about: $ 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. ~BAS > 4) pray > > 5) after fsck will end it successfully (it should), create gmirror with > the disk you checked > > gmirror label <options> gmirror-name /dev/thedisk > > 6) reboot and start the system. should go well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1203698632.10391.130.camel>