Date: Mon, 29 Nov 2004 21:53:49 +0100 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Terje Elde <terje@elde.org> Cc: freebsd-geom@freebsd.org Subject: Re: mirror handling of broken harddrives Message-ID: <20041129205349.GC753@zaphod.nitro.dk> In-Reply-To: <20041129133521.GE90910@calleigh.elde.net> References: <20041129114740.GD90910@calleigh.elde.net> <20041129115717.GA753@zaphod.nitro.dk> <20041129133521.GE90910@calleigh.elde.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.29 14:35:21 +0100, Terje Elde wrote: > On Mon, Nov 29, 2004 at 12:57:17PM +0100, Simon L. Nielsen wrote: > > ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D152911 > > ad0: FAILURE - WRITE_DMA timed out > > GEOM_MIRROR: Request failed (error=3D5). ad0[WRITE(offset=3D78290432, l= ength=3D16384)] > > GEOM_MIRROR: Device boot: provider ad0 disconnected. > > GEOM_MIRROR: Device boot: provider ad0 detected. > > GEOM_MIRROR: Device boot: rebuilding provider ad0. > > GEOM_MIRROR: Device boot: rebuilding provider ad0 finished. > > GEOM_MIRROR: Device boot: provider ad0 activated. > > > > So, it just works :-). > > Hmm, yes. But does it work the way it should? > > I mean, if the reason for the problem is that the hardware ad0 is defect,= then > you'll try to rebuild it again and again. Every time you're trying to wr= ite a > defect sector, the disk will block. That has not been the case for me. The system has run without problems for a couple of months with those rebuilds. It's two old 10GB IBM disks which are only used for the root file system (since my SATA and RAID controllers conflict so I can't boot from them). Since newer ATA drivers has remapping of bad sectors, if there really is a problem with a bad sector that cause an error, rebuilding the array should cause the bad sector to be remapped. It should also be noted that two SATA disks in the same system running another mirror has not had any of those self rebuilds. > Since this is a DMA timeout, I imagine the blocking can quite easily lead= to > other problems as well, for things sharing the same DMA channel. I don't really think the timeout is related to DMA, just the disk not responding for whatever reason (could be it's doing thermal recalibration). The disks are too old to have proper SMART support so I can see if there are actual errors. --=20 Simon L. Nielsen --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBq4xdh9pcDSc1mlERAnTHAKCEa7WAl0VFkistbJcIOenZYNsO0ACgkNv4 IMrEASC6zNwNUMfOgbwhzl4= =svJa -----END PGP SIGNATURE----- --Pk6IbRAofICFmK5e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129205349.GC753>