On May 10, 2010, at 6:28 PM, Cindy Swearingen wrote:
Hi Eduardo,
Please use the following steps to collect more information:
1. Use the following command to get the PID of the zpool import
process,
like this:
# ps -ef | grep zpool
2. Use the actual <PID of zpool import> found in step 1 in the
following
command, like this:
echo "0t<PID of zpool import>::pid2proc|::walk thread|::findstack" |
mdb -k
Then, send the output.
Hi Cindy,
first of all, thank you for taking your time to answer my question.
Here's the output of the command you requested:
# echo "0t733::pid2proc|::walk thread|::findstack" | mdb -k
stack pointer for thread ffffffff94e4db40: fffffe8000d3e5b0
[ fffffe8000d3e5b0 _resume_from_idle+0xf8() ]
fffffe8000d3e5e0 swtch+0x12a()
fffffe8000d3e600 cv_wait+0x68()
fffffe8000d3e640 txg_wait_open+0x73()
fffffe8000d3e670 dmu_tx_wait+0xc5()
fffffe8000d3e6a0 dmu_tx_assign+0x38()
fffffe8000d3e700 dmu_free_long_range_impl+0xe6()
fffffe8000d3e740 dmu_free_long_range+0x65()
fffffe8000d3e790 zfs_trunc+0x77()
fffffe8000d3e7e0 zfs_freesp+0x66()
fffffe8000d3e830 zfs_space+0xa9()
fffffe8000d3e850 zfs_shim_space+0x15()
fffffe8000d3e890 fop_space+0x2e()
fffffe8000d3e910 zfs_replay_truncate+0xa8()
fffffe8000d3e9b0 zil_replay_log_record+0x1ec()
fffffe8000d3eab0 zil_parse+0x2ff()
fffffe8000d3eb30 zil_replay+0xde()
fffffe8000d3eb50 zfsvfs_setup+0x93()
fffffe8000d3ebc0 zfs_domount+0x2e4()
fffffe8000d3ecc0 zfs_mount+0x15d()
fffffe8000d3ecd0 fsop_mount+0xa()
fffffe8000d3ee00 domount+0x4d7()
fffffe8000d3ee80 mount+0x105()
fffffe8000d3eec0 syscall_ap+0x97()
fffffe8000d3ef10 _sys_sysenter_post_swapgs+0x14b()
The first message from this thread has three files attached with
information from truss (tracing zpool import), zdb output and the
entire list of threads taken from 'echo "::threadlist -v" | mdb -k'.
Thanks,
Eduardo Bragatto
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
