On 1/25/16 22:50 , Fred Liu wrote: > [root@pluto /zones/debug]# ls -la > total 4818285 > drwxr-xr-x 2 root root 5 Jan 26 14:16 . > drwxr-xr-x 16 root root 19 Jan 25 19:21 .. > -rw-r--r-- 1 root root 2 Jan 26 14:15 bounds > -rw-r--r-- 1 root root 1056 Jan 26 14:15 METRICS.csv > -rw-r--r-- 1 root root 4305518592 Jan 26 14:15 vmdump.0 > [root@pluto /zones/debug]# mdb -f vmdump.0 >> echo ::zio_state > mdb: failed to dereference symbol: operation not supported by target > > ::status > debugging file 'vmdump.0' (object file) > > [root@pluto /zones/debug]# echo "::zio_state" | mdb -f vmdump.0 > invalid command '::zio_state': unknown dcmd name > > It looks like I can't find too much useful info here.
You don't want to be using mdb -f on a system dump. Instead here, I would go into that directory, run `savecore -vf vmdump.0 .`. That will create a unix.0 and vmcore.0 which you can then access with mdb by running `mdb 0` in that directory. Note that by using mdb -f, you've asked mdb not to interpret the core dump, but rather treat it as a raw file which is why the dcmds are not being found. Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
