# [OmniOS-discuss] device probe related command timeouts

John Barfield john.barfield at bissinc.com
Wed Jan 4 22:34:03 UTC 2017

- Previous message: [OmniOS-discuss] device probe related command timeouts
- Next message: [OmniOS-discuss] device probe related command timeouts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    So odd thing about this server….there is NO “/dev/rdsk/c14t0d0s0” anywhere.

    I wonder what that’s all about

    On 1/4/17, 3:17 PM, "John Barfield" <john.barfield at bissinc.com> wrote:

        You’re awesome! Its hanging on “open /dev/rdsk/c14t0d0s0”

        Looking at that disk now.

        On 1/4/17, 3:15 PM, "Joshua M. Clulow" <josh at sysmgr.org> wrote:

            On 4 January 2017 at 13:09, John Barfield <john.barfield at bissinc.com> wrote:
            > It actually finally completed. Doing it again with the proper PID as suggested provides the following:
            > root at PRD-GIP-cpls-san1:/export/home/jbarfield# mdb -k
            >> 0t19448::pid2proc | ::walk thread | ::findstack -v
            > stack pointer for thread ffffff2490590000: ffffff010a286750
            > [ ffffff010a286750 _resume_from_idle+0xf4() ]
            >   ffffff010a286780 swtch+0x141()
            >   ffffff010a2867c0 sema_p+0x1c7(ffffff26e094b600)
            >   ffffff010a286800 biowait+0xa4(ffffff26e094b540)
            >   ffffff010a2868d0 scsi_uscsi_handle_cmd+0x127(c100000d40, 1, ffffff24907f3da8, fffffffff7b159b0, 0, ffffff27c23171e8)
            >   ffffff010a286960 sd_ssc_send+0x136(ffffff24227d4e00, ffffff010a286970, 80000000, 1, 0)
            >   ffffff010a286a30 sd_send_scsi_TEST_UNIT_READY+0x121(ffffff24227d4e00, 1)
            >   ffffff010a286b40 sd_get_media_info_com+0xaf(c100000d40, ffffff010a286b50, ffffff010a286b54, ffffff010a286b58, 0)
            >   ffffff010a286ba0 sd_get_media_info+0x41(c100000d40, 8047330, 100005)
            >   ffffff010a286c80 sdioctl+0xc57(c100000d40, 42a, 8047330, 100005, ffffff24930f7580, ffffff010a286e68)
            >   ffffff010a286cc0 cdev_ioctl+0x39(c100000d40, 42a, 8047330, 100005, ffffff24930f7580, ffffff010a286e68)
            >   ffffff010a286d10 spec_ioctl+0x60(ffffff2492b62d80, 42a, 8047330, 100005, ffffff24930f7580, ffffff010a286e68, 0)
            >   ffffff010a286da0 fop_ioctl+0x55(ffffff2492b62d80, 42a, 8047330, 100005, ffffff24930f7580, ffffff010a286e68, 0)
            >   ffffff010a286ec0 ioctl+0x9b(3, 42a, 8047330)
            >   ffffff010a286f10 _sys_sysenter_post_swapgs+0x149()

            OK, it seems that we're hanging while sending a TEST UNIT READY to
            some device.  It's probably easiest to just use truss(1), here; e.g.:

                truss -t "open,ioctl" -f diskinfo

            Once it starts hanging, you should be able to see which open(2) and
            ioctl(2) calls happened just before the hang.

            Cheers.

            --
            Joshua M. Clulow
            UNIX Admin/Developer
            http://blog.sysmgr.org

- Previous message: [OmniOS-discuss] device probe related command timeouts
- Next message: [OmniOS-discuss] device probe related command timeouts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list