Date: Tue, 09 Apr 2013 08:45:59 -0400 From: Quartz <quartz@sneakertech.com> To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <51640D87.7070307@sneakertech.com> In-Reply-To: <FA90064E-EBB9-4091-BE47-6C893A5D33BC@FreeBSD.org> References: <2092374421.4491514.1365459764269.JavaMail.root@k-state.edu> <5163F03B.9060700@sneakertech.com> <FA90064E-EBB9-4091-BE47-6C893A5D33BC@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I hadn't followed the entire discussion, but do you have the "failmode" > zpool property set to "wait" (the default)? If so, can you reproduce it > with "failmode" set to "continue"? Yes. Changing the failmode was the first thing research led me to try. "wait" hangs almost immediately while "continue" gives me some seconds to a minute and then hangs. -STABLE has some new commits that will eventually panic the machine if this type of zfs hang goes on for too long, but that doesn't help me at all. (If I was ok with a panic, I'd set failmode to "panic" and be done with 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?51640D87.7070307>