Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vdev.unknown event #2275

Closed
behlendorf opened this issue Apr 23, 2014 · 1 comment
Closed

vdev.unknown event #2275

behlendorf opened this issue Apr 23, 2014 · 1 comment
Labels
Component: ZED ZFS Event Daemon Status: Stale No recent activity for issue

Comments

@behlendorf
Copy link
Contributor

During a scrub ZFS failed a device (correctly) but only issued a ereport.fs.zfs.vdev.unknown event. I suspect the block device driver returned an -ENODEV error and this case is not cleanly translated in to a clear eveny type. This needs to be investigated because we want to ensure all drive failure events generate clear events.

zpool events -v:
Apr 20 2014 01:01:02.829781123 ereport.fs.zfs.scrub.start
        class = "ereport.fs.zfs.scrub.start"
        ena = 0x8761deabf5700401
        detector = (embedded nvlist)
                version = 0x0
                scheme = "zfs"
                pool = 0x10dba6cff2cf314a
        (end detector)
        pool = "z"
        pool_guid = 0x10dba6cff2cf314a
        pool_context = 0x0
        pool_failmode = "wait"
        time = 0x53537ebe 0x31757483 

Apr 20 2014 01:11:45.892907702 ereport.fs.zfs.vdev.unknown
        class = "ereport.fs.zfsv"
        ena = 0x90bd7708adc02401
        detector = (embedded nvlist)
                version = 0x0
                scheme = "zfs"
                pool = 0x10dba6cff2cf314a
                vdev = 0xe62a4ffec15835bc
        (end detector)
        pool = "z"
        pool_guid = 0x10dba6cff2cf314a
        pool_context = 0x0
        pool_failmode = "wait"
        vdev_guid = 0xe62a4ffec15835bc
        vdev_type = "disk"
        vdev_path = "/dev/disk/by-vdev/z16-part1"
        vdev_ashift = 0x9
        vdev_complete_ts = 0xd890bc7a4c3df
        vdev_delta_ts = 0xbcad
        parent_guid = 0x551bfb4df624a751
        parent_type = "raidz"
        prev_state = 0x1
        time = 0x53538141 0x3538b0b6 

Apr 20 2014 07:40:44.088991778 ereport.fs.zfs.scrub.finish
        class = "ereport.fs.zfs.scrub.finish"
        ena = 0xe45b0412ee801801
        detector = (embedded nvlist)
                version = 0x0
                scheme = "zfs"
                pool = 0x10dba6cff2cf314a
        (end detector)
        pool = "z"
        pool_guid = 0x10dba6cff2cf314a
        pool_context = 0x0
        pool_failmode = "wait"
        time = 0x5353dc6c 0x54de822 

zpool status
  pool: z
 state: DEGRADED
status: One or more devices could not be used because the label is missing or
    invalid.  Sufficient replicas exist for the pool to continue
    functioning in a degraded state.
action: Replace the device using 'zpool replace'.
   see: http://zfsonlinux.org/msg/ZFS-8000-4J
  scan: scrub repaired 0 in 6h39m with 0 errors on Sun Apr 20 07:40:44 2014
config:

    NAME        STATE     READ WRITE CKSUM
    z           DEGRADED     0     0     0
      raidz3-0  DEGRADED     0     0     0
        z01     ONLINE       0     0     0
        z02     ONLINE       0     0     0
        z03     ONLINE       0     0     0
        z04     ONLINE       0     0     0
        z05     ONLINE       0     0     0
        z06     ONLINE       0     0     0
        z07     ONLINE       0     0     0
        z08     ONLINE       0     0     0
        z09     ONLINE       0     0     0
        z10     ONLINE       0     0     0
        z11     ONLINE       0     0     0
        z12     ONLINE       0     0     0
        z13     ONLINE       0     0     0
        z14     ONLINE       0     0     0
        z15     ONLINE       0     0     0
        z16     UNAVAIL      0     0     0

errors: No known data errors

dmesg

[3807962.547561] mptscsih: ioc1: attempting task abort! (sc=ffff88061db32a00)
[3807962.547567] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 78 00 00 58 00
[3807967.017822] mptbase: ioc1: LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000) cb_idx mptscsih_io_done
[3807967.018361] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff88061db32a00)
[3807967.018366] mptscsih: ioc1: attempting task abort! (sc=ffff88061ea3ad00)
[3807967.018370] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 10 00 00 18 00
[3807967.018381] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff88061ea3ad00)
[3807967.018384] mptscsih: ioc1: attempting task abort! (sc=ffff8803203d2a00)
[3807967.018387] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 d0 00 00 68 00
[3807967.018396] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff8803203d2a00)
[3807967.018399] mptscsih: ioc1: attempting task abort! (sc=ffff88031f297d00)
[3807967.018402] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 f8 00 00 88 00
[3807967.018411] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff88031f297d00)
[3807967.018414] mptscsih: ioc1: attempting task abort! (sc=ffff88031f296600)
[3807967.018417] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 98 00 00 10 00
[3807967.018426] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff88031f296600)
[3807967.018429] mptscsih: ioc1: attempting task abort! (sc=ffff8800995db500)
[3807967.018431] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 80 00 00 f0 00
[3807967.018440] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff8800995db500)
[3807967.018443] mptscsih: ioc1: attempting task abort! (sc=ffff8803c1026a00)
[3807967.018446] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c7 18 00 00 b0 00
[3807967.018455] mptscsih: ioc1: task abort: SUCCESS (rv=2002) (sc=ffff8803c1026a00)
[3807967.018474] mptscsih: ioc1: attempting target reset! (sc=ffff88061db32a00)
[3807967.018477] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 78 00 00 58 00
[3807967.018487] mptscsih: ioc1: target reset: FAILED (sc=ffff88061db32a00)
[3807967.018507] mptscsih: ioc1: attempting host reset! (sc=ffff8803c1026a00)
[3807967.018512] mptbase: ioc1: Initiating recovery
[3807979.039458] mptscsih: ioc1: host reset: SUCCESS (sc=ffff8803c1026a00)
[3807989.038545] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038550] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038553] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038555] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038558] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038560] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.038562] sd 6:0:7:0: Device offlined - not ready after error recovery
[3807989.042593] sd 6:0:7:0: rejecting I/O to offline device
[3807989.043284] sd 6:0:7:0: [sdq] killing request
[3807989.043289] sd 6:0:7:0: rejecting I/O to offline device
[3807989.043968] sd 6:0:7:0: [sdq] killing request
[3807989.043970] sd 6:0:7:0: rejecting I/O to offline device
[3807989.044419] sd 6:0:7:0: [sdq] killing request
[3807989.044423] sd 6:0:7:0: rejecting I/O to offline device
[3807989.044718] sd 6:0:7:0: [sdq] killing request
[3807989.044722] sd 6:0:7:0: rejecting I/O to offline device
[3807989.044728] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.044731] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.044735] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 d0 00 00 68 00
[3807989.044742] end_request: I/O error, dev sdq, sector 207013328
[3807989.045922] sd 6:0:7:0: [sdq] killing request
[3807989.045928] sd 6:0:7:0: rejecting I/O to offline device
[3807989.046643] sd 6:0:7:0: [sdq] killing request
[3807989.046647] sd 6:0:7:0: rejecting I/O to offline device
[3807989.047341] sd 6:0:7:0: [sdq] killing request
[3807989.047347] sd 6:0:7:0: rejecting I/O to offline device
[3807989.048037] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.048039] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.048043] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 f8 00 00 88 00
[3807989.048051] end_request: I/O error, dev sdq, sector 207013368
[3807989.048104] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.048107] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.048110] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c5 78 00 00 58 00
[3807989.048117] end_request: I/O error, dev sdq, sector 207013240
[3807989.048128] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.048133] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.048141] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 10 00 00 18 00
[3807989.048163] end_request: I/O error, dev sdq, sector 207013392
[3807989.048174] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.048178] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.048186] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c7 18 00 00 b0 00
[3807989.048209] end_request: I/O error, dev sdq, sector 207013656
[3807989.048580] sd 6:0:7:0: rejecting I/O to offline device
[3807989.048758] sd 6:0:7:0: rejecting I/O to offline device
[3807989.052466] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.052472] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.052478] sd 6:0:7:0: rejecting I/O to offline device
[3807989.053185] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 98 00 00 10 00
[3807989.053196] end_request: I/O error, dev sdq, sector 207013528
[3807989.054037] sd 6:0:7:0: [sdq] Unhandled error code
[3807989.054041] sd 6:0:7:0: [sdq]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[3807989.054046] sd 6:0:7:0: [sdq] CDB: Read(10): 28 00 0c 56 c6 80 00 00 f0 00
[3807989.054117] end_request: I/O error, dev sdq, sector 207013504
@behlendorf behlendorf added the zed label Apr 23, 2014
@behlendorf behlendorf added this to the 0.7.0 milestone Apr 23, 2014
@behlendorf behlendorf removed this from the 0.7.0 milestone Dec 20, 2014
@rageagainstthebugs rageagainstthebugs mentioned this issue Aug 30, 2018
Closed
@stale
Copy link

stale bot commented Aug 25, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 23, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: ZED ZFS Event Daemon Status: Stale No recent activity for issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@behlendorf