On Wed, Mar 3, 2010 at 2:31 AM, Henrik Johansen <fi...@hotmail.com> wrote: > > > But this return what appears to be a hexdump as well as the zvol names and > their read counts > > [....] > 370: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 390: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 3a0: 00 f0 6a 5d 11 ff ff ff 00 d0 ef 62 11 ff ff ff ..j].......b.... > [...] > 2 > tank/intern01_lun_02 3 > > I can figure out where that comes from ... >
I haven't had much time to look at this. I've tried reproducing the problem, but I can't with the simple test I'm running. But what's happening with the hex dump you're seeing is that DTrace is trying to print something that it thinks should be a string but which contains unprintable characters. For this case, it defaults to a hex dump. What that means is that zv_name contains garbage. I'm not sure why this would be happening. Chad _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
