Date: Wed, 10 Apr 2013 15:46:11 -0400 From: Quartz <quartz@sneakertech.com> To: "Lawrence K. Chen, P.Eng." <lkchen@ksu.edu> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <5165C183.1020704@sneakertech.com> In-Reply-To: <499967956.5577199.1365621470123.JavaMail.root@k-state.edu> References: <499967956.5577199.1365621470123.JavaMail.root@k-state.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Other options are, failmode=continue is described that the system > will continue on as if nothing has changed. >Not > sure what it means the system will continue I'm not sure ether. In my experience, there's effectively no difference between "wait" and "continue". > The other option is failmode=panic. Which might be what you want in > this case, since you can't shutdown gracefully with all I/O hanging. Well, what I *WANT* is a way to kick the pool or something so that the rest of the machine still functions. As it stands, I can't even reliably get the status of the pool, as I can't reliably run half the zfs commands. ______________________________________ it has a certain smooth-brained appeal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5165C183.1020704>