Brent Jones <br...@servuhome.net> writes: >> >> I haven't figured out a way to identify the problem, still trying to >> find a 100% way to reproduce this problem. >> Seemingly the more snapshots I send at a given time, the likelihood of >> this happening goes up, but, correlation is not causation :) >> >> I might try to open a support case with Sun (have a support contract), >> but Opensolaris doesn't seem to be well understood by the support >> folks yet, so not sure how far it will get. >> >> -- >> Brent Jones >> br...@servuhome.net >> > > I can reproduce this 100% by sending about 6 or more snapshots at once. > > Here is some output that JBK helped me put together: > > Here is a pastebin 'mdb' findstack output: > http://pastebin.com/m4751b08c > > Not sure what I'm looking at, but maybe someone at Sun can see whats going on?
I've had similar issues with similar traces. I think you're waiting on a transaction that's never going to come. I thought at the time that I was hitting: CR 6367701 "hang because tx_state_t is inconsistent" But given the rash of reports here, it seems perhaps this is something different. I, like you, hit it when sending snapshots, it seems (in my case) to be specific to incremental streams, rather than full streams, I can send seemingly any number of full streams, but incremental sends via send -i, or send -R of datasets with multiple snapshots, will get into a state like that above. -- Rich _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
