Date: Tue, 16 Nov 2010 11:24:48 +0100 From: Olivier Smedts <olivier@gid0.org> To: Michael Boers <michaelscotttech@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: zfs mirror recognizing disk failures Message-ID: <AANLkTi=mqgjj%2BdWVvZKmUcZWPtZSF2wA=upYy%2B1dEhRe@mail.gmail.com> In-Reply-To: <25DC6C26-52FB-447A-AEB0-8549DA8F53E7@gmail.com> References: <25DC6C26-52FB-447A-AEB0-8549DA8F53E7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/11/15 Michael Boers <michaelscotttech@gmail.com>: > Is there anything I can do to make a zfs mirror quicker to give up on a > flaky disk? > > I recently had a 100% zfs system crash when started to have some disk > errors. =A0I had hoped that by having a mirror, the system would survive = this > type of error. =A0Instead it just hung. You can offline the faulty drive. Also, I think you're interested in a feature like TLER : http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery But typical (cheap) drives don't implement it. > > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): SYNCHRONIZE CACHE(10). > CDB: 35 0 0 0 0 0 0 0 0 0 > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): CAM Status: SCSI Status > Error > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): SCSI Status: Check > Condition > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): ABORTED COMMAND asc:0,0 > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): No additional sense > information > Nov 11 10:05:01 caprica kernel: (da2:mpt0:0:3:0): Retries Exhausted > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003c87a0:2838 tim= ed > out for ccb 0xffffff0103acc000 (req->ccb 0xffffff0103acc000) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003c5110:2839 tim= ed > out for ccb 0xffffff035cab0800 (req->ccb 0xffffff035cab0800) > Nov 11 10:05:53 caprica kernel: mpt0: attempting to abort req > 0xffffff80003c87a0:2838 function 0 > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003bef30:2840 tim= ed > out for ccb 0xffffff0007986800 (req->ccb 0xffffff0007986800) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003c8560:2841 tim= ed > out for ccb 0xffffff032d985000 (req->ccb 0xffffff032d985000) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003bf320:2842 tim= ed > out for ccb 0xffffff0103af2000 (req->ccb 0xffffff0103af2000) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003cbda0:2843 tim= ed > out for ccb 0xffffff0103b0b000 (req->ccb 0xffffff0103b0b000) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003bfd40:2844 tim= ed > out for ccb 0xffffff00102bf800 (req->ccb 0xffffff00102bf800) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003cad50:2845 tim= ed > out for ccb 0xffffff01e6f33000 (req->ccb 0xffffff01e6f33000) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003caf00:2846 tim= ed > out for ccb 0xffffff01e6f24800 (req->ccb 0xffffff01e6f24800) > Nov 11 10:05:53 caprica kernel: mpt0: request 0xffffff80003ccd60:2847 tim= ed > out for ccb 0xffffff01308a4000 (req->ccb 0xffffff01308a4000) > > Is this a type of error zfs can survive or do I need a hardware mirror to > handle this type of problem? > > Thanks, > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 Olivier Smedts=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 _ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ASCII ribbon campaign ( ) e-mail: olivier@gid0.org=A0 =A0 =A0 =A0 - against HTML email & vCards=A0 X www: http://www.gid0.org=A0 =A0 - against proprietary attachments / \ =A0 "Il y a seulement 10 sortes de gens dans le monde : =A0 ceux qui comprennent le binaire, =A0 et ceux qui ne le comprennent pas."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=mqgjj%2BdWVvZKmUcZWPtZSF2wA=upYy%2B1dEhRe>