# [OmniOS-discuss] 8TB Seagates under load = PANIC?

Artem Penner apenner.it at gmail.com
Fri Mar 17 13:59:24 UTC 2017

- Previous message: [OmniOS-discuss] 8TB Seagates under load = PANIC?
- Next message: [OmniOS-discuss] 8TB Seagates under load = PANIC?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Additional info:

    > ::stack
    vpanic()
    0xfffffffffba8b1a8()
    vdev_disk_io_start+0x130(ffffd06a690b8c70)
    zio_vdev_io_start+0xae(ffffd06a690b8c70)
    zio_execute+0x78(ffffd06a690b8c70)
    vdev_queue_io_done+0x78(ffffd06af0a85708)
    zio_vdev_io_done+0x80(ffffd06af0a85708)
    zio_execute+0x78(ffffd06af0a85708)
    taskq_thread+0x2d0(ffffd06342f81020)
    thread_start+8()

    > ::status
    debugging crash dump /var/crash/unknown/vmcore.0 (64-bit) from zns2-n2
    operating system: 5.11 omnios-2fb9a48 (i86pc)
    image uuid: 32c56db4-4a94-4af4-eb2a-8fd6ed5e524f
    panic message: assertion failed: ldi_strategy(dvd->vd_lh, bp) == 0, file:
    ../../common/fs/zfs/vdev_disk.c, line: 819
    dump content: kernel pages only

    > ::spa -v
    ADDR                 STATE NAME

    ffffd06343afa000    ACTIVE pool5

        ADDR             STATE     AUX          DESCRIPTION

        ffffd06344a51380 DEGRADED  -            root
        ffffd06344a519c0 HEALTHY   -              raidz
        ffffd06344a52080 HEALTHY   -
     /dev/dsk/c9t5000CCA031039F18d0s0
        ffffd06344a526c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03103A054d0s0
        ffffd06344a52d00 HEALTHY   -
     /dev/dsk/c9t5000CCA031048B88d0s0
        ffffd06344a53340 HEALTHY   -
     /dev/dsk/c9t5000CCA031039E80d0s0
        ffffd06344a53980 HEALTHY   -
     /dev/dsk/c9t5000CCA031048C18d0s0
        ffffd06344a54040 HEALTHY   -
     /dev/dsk/c9t5000CCA031039F50d0s0
        ffffd06344a54680 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AA40d0s0
        ffffd06344a54cc0 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AD44d0s0
        ffffd06344a55300 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B274d0s0
        ffffd06344a55940 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B2C8d0s0
        ffffd06344a56000 DEGRADED  -              raidz
        ffffd06344a56640 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B34Cd0s0
        ffffd06344a56c80 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AE18d0s0
        ffffd06344a572c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AE54d0s0
        ffffd066f7ecd040 REMOVED   -                spare
        ffffd06344a57900 REMOVED   -
     /dev/dsk/c9t5000CCA03103B2D4d0s0
        ffffd0634229bd40 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AD84d0s0
        ffffd06344a580c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B26Cd0s0
        ffffd06344a58700 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B3ACd0s0
        ffffd06344a58d40 HEALTHY   -
     /dev/dsk/c9t5000CCA03103B338d0s0
        ffffd06344a59380 HEALTHY   -
     /dev/dsk/c9t5000CCA03104DFACd0s0
        ffffd06344a599c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03104ABA8d0s0
        ffffd06344a5a080 HEALTHY   -
     /dev/dsk/c9t5000CCA03103A10Cd0s0
        ffffd06344a5a6c0 HEALTHY   -              raidz
        ffffd06344a5ad00 HEALTHY   -
     /dev/dsk/c9t5000CCA02C413D04d0s0
        ffffd06344a5b340 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D40Cd0s0
        ffffd0634579c6c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D7A8d0s0
        ffffd0634579c080 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D768d0s0
        ffffd0634f2329c0 HEALTHY   -
     /dev/dsk/c9t5000CCA031046494d0s0
        ffffd0634f232380 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D458d0s0
        ffffd0634f231d40 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D408d0s0
        ffffd0634f231700 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D798d0s0
        ffffd0634f2310c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03103D28Cd0s0
        ffffd0634f228900 HEALTHY   -
     /dev/dsk/c9t5000CCA031047A30d0s0
        ffffd0634f2282c0 DEGRADED  -              raidz
        ffffd0634579d980 REMOVED   -                spare
        ffffd0634f227c80 REMOVED   -
     /dev/dsk/c9t5000CCA03104D2ECd0s0
        ffffd071db7da340 HEALTHY   -
     /dev/dsk/c9t5000CCA02C414524d0s0
        ffffd0634f227640 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D370d0s0
        ffffd0634f227000 HEALTHY   -
     /dev/dsk/c9t5000CCA031038248d0s0
        ffffd0634f226940 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D448d0s0
        ffffd0634f226300 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D81Cd0s0
        ffffd0634f225cc0 HEALTHY   -
     /dev/dsk/c9t5000CCA031038470d0s0
        ffffd0634f225680 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D400d0s0
        ffffd0634f225040 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D330d0s0
        ffffd0634f22a980 HEALTHY   -
     /dev/dsk/c9t5000CCA03104D7F8d0s0
        ffffd0634f22a340 HEALTHY   -
     /dev/dsk/c9t5000CCA031046C68d0s0
        ffffd0634f229d00 HEALTHY   -              mirror
        ffffd0634f2296c0 HEALTHY   -
     /dev/dsk/c9t500003979C88FF91d0s0
        ffffd0634f229080 HEALTHY   -
     /dev/dsk/c9t500003973C88B6F5d0s0
        ffffd0634f2209c0 HEALTHY   -              mirror
        ffffd0634f220380 HEALTHY   -
     /dev/dsk/c9t500003979C88FF5Dd0s0
        ffffd0634f21fd40 HEALTHY   -
     /dev/dsk/c9t500003979C890019d0s0
        -                -         -            cache
        ffffd06352e1d640 HEALTHY   -
     /dev/dsk/c9t5000CCA04B12952Cd0s0
        ffffd06352e1d000 HEALTHY   -
     /dev/dsk/c9t5000CCA04B12A1D0d0s0
        -                -         -            spares
        ffffd06352e1e2c0 HEALTHY   -
     /dev/dsk/c9t5000CCA03104AD84d0s0
        ffffd06352e1dc80 HEALTHY   -
     /dev/dsk/c9t5000CCA02C414524d0s0
    ffffd063157c9000    ACTIVE rpool

        ffffd063160dc340 HEALTHY   -            root
        ffffd062a21b4040 HEALTHY   -              /dev/dsk/c3t8d1s0

    пт, 17 мар. 2017 г. в 16:25, Artem Penner <apenner.it at gmail.com>:

    Thank a lot,

    >> As for the busy filesystem, I wonder if it'll behave better after your
    resilver finishes?  Otherwise, I'm not immediately sure what to tell you.
    I will certainly report the result after resilver finished.

    >> And one last thing... I'm travelling back home today, so I'll be
    unavailable in a couple of hours.
    It's not production. We are only testing the fault tolerance before
    entering it to production use.

    ----------
    PS: Thank you very much, it feels like Sun Microsystem is alive again and
    you applied to the most qualified support ever.

    пт, 17 мар. 2017 г. в 16:12, Dan McDonald <danmcd at omniti.com>:

    Thank you.

    So you're running LTS, AND it is up to date as of today.  This helps me
    understand some things. IF this was fixed already in later releases (under
    a different bug id), we likely deemed it too big/intrusive to backport to
    an LTS release, or we overlooked its importance.

    As for the busy filesystem, I wonder if it'll behave better after your
    resilver finishes?  Otherwise, I'm not immediately sure what to tell you.

    And one last thing... I'm travelling back home today, so I'll be
    unavailable in a couple of hours.

    Dan
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20170317/c2ad90d5/attachment-0001.html>

- Previous message: [OmniOS-discuss] 8TB Seagates under load = PANIC?
- Next message: [OmniOS-discuss] 8TB Seagates under load = PANIC?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list