I certainly have not debugged this to a level necessary to have isolated exactly what happened here. But my gut, yes I know that's very technical, tells me this is a dedup issue. For one, the sort of issue I'm seeing seems to be consistent with the sort of issues you might expect from an error in code doing what dedup does, and two it is new code as of this build, I believe, and I was making use of it turning it on and off and coping and deleting files under its purview, something I believe would stress it quite a bit.
Yes, I recommend not using b134 for anything important, and most of all I recommend not enabling dedup if at all avoidable, at least make sure you are maintaining a running back up on another physical pool. -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
