Date: Tue, 9 Apr 2013 14:06:24 +0200 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: Quartz <quartz@sneakertech.com> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <FA90064E-EBB9-4091-BE47-6C893A5D33BC@FreeBSD.org> In-Reply-To: <5163F03B.9060700@sneakertech.com> References: <2092374421.4491514.1365459764269.JavaMail.root@k-state.edu> <5163F03B.9060700@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez Quartz w dniu 9 kwi 2013, o godz. 12:40: >=20 >> So, you're not really waiting a long time.... >=20 > I still don't think you're 100% clear on what's happening in my case. = I'm trying to explain that my problem is *prior* to the motherboard = resetting, NOT after. If I hard-reset the machine with the front panel = switch, it boots just fine every time. >=20 > When my pool *FAILS* (ie; is unrecoverable because I lost too many = drives) it hangs effectively all io on the entire machine. I can't cd or = ls directories, I can't run any zfs commands, and I can't issue a reboot = or halt. This is a hang. The machine is completely useless in this = state. There is no disk or cpu activity churning. There's no pool = (anymore) to be trying to resilver or whatever anyway. 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"? --=20 If you cut off my head, what would I say? Me and my head, or me and my = body?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FA90064E-EBB9-4091-BE47-6C893A5D33BC>