On Thu, Oct 9, 2008 at 10:18 AM, Mike Gerdts <[EMAIL PROTECTED]> wrote: > On Thu, Oct 9, 2008 at 10:10 AM, Greg Shaw <[EMAIL PROTECTED]> wrote: >> Nevada isn't production code. For real ZFS testing, you must use a >> production release, currently Solaris 10 (update 5, soon to be update 6). > > I misstated before in my LDoms case. The corrupted pool was on > Solaris 10, with LDoms 1.0. The control domain was SX*E, but the > zpool there showed no problems. I got into a panic loop with dangling > dbufs. My understanding is that this was caused by a bug in the LDoms > manager 1.0 code that has been fixed in a later release. It was a > supported configuration, I pushed for and got a fix. However, that > pool was still lost.
Or maybe it wasn't fixed yet. I see that this was committed just today. 6684721 file backed virtual i/o should be synchronous http://hg.genunix.org/onnv-gate.hg/rev/eb40ff0c92ec -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
