Date: Tue, 09 Apr 2013 12:22:10 -0400 From: Quartz <quartz@sneakertech.com> To: Tom Evans <tevans.uk@googlemail.com> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <51644032.7070305@sneakertech.com> In-Reply-To: <51643F91.30704@sneakertech.com> References: <2092374421.4491514.1365459764269.JavaMail.root@k-state.edu> <5163F03B.9060700@sneakertech.com> <CAFHbX1LO9OvbqyYYaob-7nQSA_dwQkMK7%2Bvn9c4QrXQuKvTCFA@mail.gmail.com> <51640BDB.1020403@sneakertech.com> <CAFHbX1%2BcdUtumDk3BB1jSE0sCuvVwsTNCAs8e=T0iML6WxHASw@mail.gmail.com> <51643F91.30704@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I don't know the ahci/cam stack from a hole in the wall, but it seems to > me that if it can gracefully handle two drives dropping out and coming > back randomly, it ought to be able to handle three. I suppose it's > possible that zfs itself is not the root cause of the problem, but one > way or another there's some kind of interaction here, as I only > experience an issue when the pool is no longer solvent. Although, if there's some way I can definitively test to see if it's an ahci/cam issue or not, I'll be glad to try 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?51644032.7070305>