Date: Sat, 13 Apr 2013 17:23:38 -0400 From: Quartz <quartz@sneakertech.com> To: Jeremy Chadwick <jdc@koitsu.org> Cc: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <5169CCDA.2020901@sneakertech.com> In-Reply-To: <5169C747.8030806@sneakertech.com> References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org> <51672164.1090908@o2.pl> <20130411212408.GA60159@icarus.home.lan> <5168821F.5020502@o2.pl> <20130412220350.GA82467@icarus.home.lan> <516917CA.5040607@sneakertech.com> <20130413154130.GA877@icarus.home.lan> <5169C747.8030806@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Your issue: "on my raidz2 pool, when I lose more than 2 disks, I/O to >> the pool stalls indefinitely, > > Close, but not quite- Yes, io to the pool stalls, but io in general also > stalls. It appears the problem possibly doesn't start until there's io > traffic to the pool though. > > >> but I can still use the system barring >> ZFS-related things; > > No. I've responded to this misconception on your part more than once- I > *CANNOT* use the system in any reliable way, random commands fail. I've > had it hang trying cd from one dir on the boot volume to another dir on > the boot volume. The only thing I can *reliably* do is log in. Past that > point all bets are off. So, in looking over my thread again from the start, I realize there's been an evolution of diagnosis that may not have been immediately obvious. When I wrote up the description in my initial email, *at that time* I thought that io confined to the boot drive was in the clear. However, shortly afterwards after doing more tests over the course of the thread, I discovered that this was NOT the case. ______________________________________ it has a certain smooth-brained appeal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5169CCDA.2020901>