Log files are getting big enough that I'm going to strart attaching them as files rather than inlining them - if this is poor practice, let me know.
So after my last test failed to show exec for zfs, I changed my DTrace script to simply log all exec calls, along with PID and PPID, to hopefully show a history of who is calling what. Both the current script and a failure log are attached. As I read these, it appears to me that zoneadmd is calling /usr/lib/fs/zfs/umount (which becomes 'zfs' somehow?), and hastorageplus_postnet_stop is getting called before the zfs unmount initiated by zoneadmd is complete. So it seems to me that the HAStoragePlus is not waiting for the zone stop to complete. I'm not sure how to tell DTrace to log the sequencing of this except by guessing based on timestamps. Is it possible for DTrace to show when the smb1_zone resource actually thinks it is fully stopped, and when the smb1_zpool resource thinks it should begin the 'stop' process? For reference: root at mltproc1:~# clrs show -p Resource_dependencies smb1_zone === Resources === Resource: smb1_zone Resource_dependencies: smb1_lhname smb1_zpool --- Standard and extension properties --- -- This message posted from opensolaris.org -------------- next part -------------- A non-text attachment was scrubbed... Name: umount2.d Type: application/octet-stream Size: 802 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/ha-clusters-discuss/attachments/20091210/7dfd10d4/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: umount.failed.3.log.gz Type: application/octet-stream Size: 4511 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/ha-clusters-discuss/attachments/20091210/7dfd10d4/attachment-0001.obj>
