Date: Sat, 13 Apr 2013 04:31:06 -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: <516917CA.5040607@sneakertech.com> In-Reply-To: <20130412220350.GA82467@icarus.home.lan> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
>If the ZFS layer > is waiting on CAM, and CAM is waiting on your hardware, then those I/O > requests are going to block indefinitely. > 2. I agree that the problem is not likely in ZFS, but rather either with > CAM, the AHCI implementation used, or hardware (either disk or storage > controller). Question: How (or does) this relate to the hang that I'm seeing with my system? You mentioned cam issues when talking to me earlier, but less decisively than your comment here. What's the difference? > We're also > going to need to see "zpool status" output, as well as "zpool get all" > and "zfs get all". "pciconf -lvbc" would also be useful. You never asked for these when talking to me, but I can provide any of it if you want to look at it. ______________________________________ it has a certain smooth-brained appeal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?516917CA.5040607>