On Wed, Nov 18, 2009 at 10:30 AM, Richard Elling <richard.ell...@gmail.com>wrote:
> On Nov 18, 2009, at 5:44 AM, Jacob Ritorto wrote: > > Hi all, >> Not sure if you missed my last response or what, but yes, the pool >> is set to wait because it's one of many pools on this prod server and we >> can't just panic everything because one pool goes away. >> >> I just need a way to reset one pool that's stuck. >> >> If the architecture of zfs can't handle this scenario, I understand >> and can rework the layout. >> > > ZFS relies on the underlying drivers to report errors. For iSCSI > initiator, > the default timeout is 180 seconds. This was fixed, but is now tunable > (b121). > -- richard > > Just let me know one way or the other, please. >> >> thx >> jake >> >> > Also, I never said anything about setting it to panic. I'm not sure why you can't set it to continue while alerting you that a vdev has failed? -- --Tim
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
