Date: Thu, 11 Apr 2013 22:03:04 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: =?iso-8859-1?Q?Radio_mlodych_bandyt=F3w?= <radiomlodychbandytow@o2.pl> Cc: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <41A207817BC94167B0C94133EC0DFD68@multiplay.co.uk> References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org> <51672164.1090908@o2.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Radio mlodych bandytów" <radiomlodychbandytow@o2.pl> > Seeing a ZFS thread, I decided to write about a similar problem that I experience. > I have a failing drive in my array. I need to RMA it, but don't have time and it fails rarely enough to be a yet another > annoyance. > The failure is simple: it fails to respond. > When it happens, the only thing I found I can do is switch consoles. Any command fails, login fails, apps hang. > > On the 1st console I see a series of messages like: > > (ada0:ahcich0:0:0:0): CAM status: Command timeout > (ada0:ahcich0:0:0:0): Error 5, Periph was invalidated > (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED > > I use RAIDZ1 and I'd expect that none single failure would cause the system to fail... OS version? ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A207817BC94167B0C94133EC0DFD68>