replace offline or FAULTED device in ZPOOL

最新推荐文章于 2023-02-20 11:28:28 发布
最新推荐文章于 2023-02-20 11:28:28 发布
阅读量920 收藏 1
点赞数
文章标签： php
原文链接：https://yq.aliyun.com/articles/18133
版权
今早发现一台zfsonlinux主机的zpool其中一块硬盘写错误次数过多变成FAULTED状态了, raidz1的话变成了DEGRADED状态.
但是hot spare还是AVAIL的状态, 也就是说hot spare没有自动用起来.
(后来发现确实如此, hot spare不会自动使用, 需要手工干预)
当前的zpool状态, sdl已经faulted了. 
[root@db-192-168-173-219 ~]# zpool status zp1
  pool: zp1
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: none requested
config:

        NAME                                            STATE     READ WRITE CKSUM
        zp1                                             DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            sdb                                         ONLINE       0     0     0
            sdc                                         ONLINE       0     0     0
            sdd                                         ONLINE       0     0     0
            sde                                         ONLINE       0     0     0
            sdf                                         ONLINE       0     0     0
            sdg                                         ONLINE       0     0     0
            sdh                                         ONLINE       0     0     0
            sdi                                         ONLINE       0     0     0
            sdj                                         ONLINE       0     0     0
            sdk                                         ONLINE       0     0     0
            sdl                                         FAULTED     11   586     0  too many errors
        logs
          scsi-36c81f660eb18e8001af8e4ec0420e21f-part4  ONLINE       0     0     0
        spares
          scsi-36c81f660eb18e8001b32c5c61a48318a        AVAIL   

errors: No known data errors

从dmesge中可以读到大量的错误信息.
 
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 93 be f0 00 00 08 00
INFO: task txg_sync:25712 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
txg_sync      D 0000000000000000     0 25712      2 0x00000080
 ffff8804ddaa7b70 0000000000000046 0000000000000001 ffff880232635530
 0000000000000000 0000000000000000 ffff8804ddaa7af0 ffffffff81065e02
 ffff8804ddb8b058 ffff8804ddaa7fd8 000000000000fbc8 ffff8804ddb8b058
Call Trace:
 [<ffffffff81065e02>] ? default_wake_function+0x12/0x20
 [<ffffffff810a70a1>] ? ktime_get_ts+0xb1/0xf0
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffffa02e7480>] ? zio_execute+0x0/0x140 [zfs]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa02787e3>] dsl_pool_sync+0xb3/0x440 [zfs]
 [<ffffffffa028c67b>] spa_sync+0x40b/0xae0 [zfs]
 [<ffffffffa02a0bb4>] txg_sync_thread+0x384/0x5e0 [zfs]
 [<ffffffff81059329>] ? set_user_nice+0xc9/0x130
 [<ffffffffa02a0830>] ? txg_sync_thread+0x0/0x5e0 [zfs]
 [<ffffffffa016f948>] thread_generic_wrapper+0x68/0x80 [spl]
 [<ffffffffa016f8e0>] ? thread_generic_wrapper+0x0/0x80 [spl]
 [<ffffffff8109aef6>] kthread+0x96/0xa0
 [<ffffffff8100c20a>] child_rip+0xa/0x20
 [<ffffffff8109ae60>] ? kthread+0x0/0xa0
 [<ffffffff8100c200>] ? child_rip+0x0/0x20
INFO: task nfsd:28814 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
nfsd          D 0000000000000006     0 28814      2 0x00000080
 ffff8806d77adab0 0000000000000046 0000000000000000 0000000000000003
 0000000000000001 0000000000000086 ffff8806d77ada60 ffffffff81058d53
 ffff8806d7497098 ffff8806d77adfd8 000000000000fbc8 ffff8806d7497098
Call Trace:
 [<ffffffff81058d53>] ? __wake_up+0x53/0x70
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa02e8473>] ? zio_nowait+0xb3/0x170 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa02e39e0>] zil_commit+0x3b0/0x700 [zfs]
 [<ffffffffa02d83e2>] zfs_fsync+0x92/0x120 [zfs]
 [<ffffffffa02ee8ee>] zpl_commit_metadata+0x3e/0x60 [zfs]
 [<ffffffffa04f8e10>] commit_metadata+0x40/0x70 [nfsd]
 [<ffffffff8119775e>] ? fsnotify_create+0x5e/0x80
 [<ffffffff811983dc>] ? vfs_create+0xfc/0x110
 [<ffffffffa04fc444>] nfsd_create_v3+0x444/0x530 [nfsd]
 [<ffffffffa0503c13>] nfsd3_proc_create+0x123/0x1b0 [nfsd]
 [<ffffffffa04f4425>] nfsd_dispatch+0xe5/0x230 [nfsd]
 [<ffffffffa04a37e4>] svc_process_common+0x344/0x640 [sunrpc]
 [<ffffffff81065df0>] ? default_wake_function+0x0/0x20
 [<ffffffffa04a3e20>] svc_process+0x110/0x160 [sunrpc]
 [<ffffffffa04f4b52>] nfsd+0xc2/0x160 [nfsd]
 [<ffffffffa04f4a90>] ? nfsd+0x0/0x160 [nfsd]
 [<ffffffff8109aef6>] kthread+0x96/0xa0
 [<ffffffff8100c20a>] child_rip+0xa/0x20
 [<ffffffff8109ae60>] ? kthread+0x0/0xa0
 [<ffffffff8100c200>] ? child_rip+0x0/0x20
INFO: task postgres:46313 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000004     0 46313  46300 0x00000080
 ffff8803806519b8 0000000000000082 0000000000000000 ffff880380651a08
 0000000000000001 ffff8800404c5930 ffff880623f52040 0000000000000000
 ffff8804270d3058 ffff880380651fd8 000000000000fbc8 ffff8804270d3058
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff8119938a>] ? __link_path_walk+0x7ca/0xff0
 [<ffffffff81528f0e>] ? mutex_lock+0x1e/0x50
 [<ffffffff8122752f>] ? security_inode_permission+0x1f/0x30
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:46554 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000005     0 46554  46541 0x00000080
 ffff88048fc799b8 0000000000000082 0000000000000000 ffff88048fc79a08
 0000000000000001 ffff880240a8e4a0 ffff880606aa5750 0000000000000000
 ffff8806d775f058 ffff88048fc79fd8 000000000000fbc8 ffff8806d775f058
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff814c5b8a>] ? inet_sendmsg+0x4a/0xb0
 [<ffffffff81447e03>] ? sock_sendmsg+0x123/0x150
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:46555 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000006     0 46555  46541 0x00000080
 ffff8807c1cab9b8 0000000000000086 0000000000000000 ffff8807c1caba08
 0000000000000001 ffff8801e8ea73e0 ffff88063991f230 0000000000000000
 ffff880806b9c638 ffff8807c1cabfd8 000000000000fbc8 ffff880806b9c638
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff8119938a>] ? __link_path_walk+0x7ca/0xff0
 [<ffffffff81528f0e>] ? mutex_lock+0x1e/0x50
 [<ffffffff8122752f>] ? security_inode_permission+0x1f/0x30
 [<ffffffffa017936f>] ? tsd_exit+0x5f/0x2b0 [spl]
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:47162 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000005     0 47162  47129 0x00000080
 ffff8802d1dbf9b8 0000000000000086 0000000000000000 ffff8802d1dbfa08
 0000000000000001 ffff8800bb012870 ffff880673838a80 0000000000000000
 ffff8804218f9058 ffff8802d1dbffd8 000000000000fbc8 ffff8804218f9058
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff814c5b8a>] ? inet_sendmsg+0x4a/0xb0
 [<ffffffff81528f0e>] ? mutex_lock+0x1e/0x50
 [<ffffffff81447e03>] ? sock_sendmsg+0x123/0x150
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:47184 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000004     0 47184  47129 0x00000080
 ffff8802afd519b8 0000000000000082 0000000000000000 ffff8802afd51a08
 0000000000000001 ffff88010ea124a0 ffff880373f1aa80 0000000000000000
 ffff8804260a9058 ffff8802afd51fd8 000000000000fbc8 ffff8804260a9058
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff81449ab3>] ? sock_recvmsg+0x133/0x160
 [<ffffffff8108b16e>] ? send_signal+0x3e/0x90
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:39751 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000000     0 39751  39591 0x00000080
 ffff8805dbd1b9b8 0000000000000082 0000000000000040 ffff8805dbd1ba08
 0000000000000001 ffff88020b036c40 ffff8804c9b02e58 0000000000000000
 ffff8808270125f8 ffff8805dbd1bfd8 000000000000fbc8 ffff8808270125f8
Call Trace:
 [<ffffffff810a70a1>] ? ktime_get_ts+0xb1/0xf0
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff810a70a1>] ? ktime_get_ts+0xb1/0xf0
 [<ffffffff81447e03>] ? sock_sendmsg+0x123/0x150
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:12310 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000000     0 12310  39591 0x00000080
 ffff8804844bd9b8 0000000000000086 0000000000000040 ffff8804844bda08
 0000000000000001 ffff8803319737b0 ffff8803b97b06a8 0000000000000000
 ffff880583917af8 ffff8804844bdfd8 000000000000fbc8 ffff880583917af8
Call Trace:
 [<ffffffff810a70a1>] ? ktime_get_ts+0xb1/0xf0
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff81449ab3>] ? sock_recvmsg+0x133/0x160
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
INFO: task postgres:19243 blocked for more than 120 seconds.
      Tainted: P           ---------------    2.6.32-431.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
postgres      D 0000000000000000     0 19243  46300 0x00000080
 ffff8801c2fe59b8 0000000000000086 0000000000000000 ffff8801c2fe5a08
 0000000000000001 ffff88001beec250 ffff88021e804fa0 0000000000000000
 ffff880421903af8 ffff8801c2fe5fd8 000000000000fbc8 ffff880421903af8
Call Trace:
 [<ffffffff815280a3>] io_schedule+0x73/0xc0
 [<ffffffffa0177bcc>] cv_wait_common+0xac/0x1c0 [spl]
 [<ffffffff8109b2a0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa024dde9>] ? dbuf_rele_and_unlock+0x169/0x210 [zfs]
 [<ffffffffa0177cf8>] __cv_wait_io+0x18/0x20 [spl]
 [<ffffffffa02e76bb>] zio_wait+0xfb/0x1b0 [zfs]
 [<ffffffffa0264805>] dmu_tx_count_write+0x695/0x6f0 [zfs]
 [<ffffffff8116fc6c>] ? __kmalloc+0x20c/0x220
 [<ffffffffa016e20f>] ? kmem_alloc_debug+0x8f/0x4c0 [spl]
 [<ffffffffa02648af>] dmu_tx_hold_write+0x4f/0x70 [zfs]
 [<ffffffffa02dada6>] zfs_write+0x406/0xcf0 [zfs]
 [<ffffffff81449ab3>] ? sock_recvmsg+0x133/0x160
 [<ffffffff8108b16e>] ? send_signal+0x3e/0x90
 [<ffffffffa02ef3f2>] zpl_write_common+0x52/0x80 [zfs]
 [<ffffffffa02ef488>] zpl_write+0x68/0xa0 [zfs]
 [<ffffffff812263c6>] ? security_file_permission+0x16/0x20
 [<ffffffff81188f78>] vfs_write+0xb8/0x1a0
 [<ffffffff81189871>] sys_write+0x51/0x90
 [<ffffffff810e1e5e>] ? __audit_syscall_exit+0x25e/0x290
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 a4 ae 60 00 00 08 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 75 e4 08 00 00 08 00
scanning ...
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10)
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 50 4a 60 00 00 10 00
: 28 00 00 00 0a 10 00 00 10 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 67 e5 6d f8 00 00 08 00
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 66 95 36 98 00 00 10 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 7b fe 48 00 00 08 00

sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(16): 88 00 00 00 00 01 d1 af b4 10 00 00 00 10 00 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 68 93 bd 78 00 00 08 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Write(10): 2a 00 68 ad 3d 20 00 00 28 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 5f 5c 66 48 00 00 08 00
sd 0:2:11:0: [sdl] Unhandled error code
sd 0:2:11:0: [sdl] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:2:11:0: [sdl] CDB: Read(10): 28 00 5f 5f 44 90 00 00 10 00
end_request: I/O error, dev sdl, sector 1715667304
end_request: I/O error, dev sdl, sector 7812920848
end_request: I/O error, dev sdl, sector 1716598240
end_request: I/O error, dev sdl, sector 2576
end_request: I/O error, dev sdl, sector 7812920336
end_request: I/O error, dev sdl, sector 7812920848


手工将fautaled的硬盘replace为hot spare盘.
 
[root@db-192-168-173-219 ~]# zpool replace zp1 sdl scsi-36c81f660eb18e8001b32c5c61a48318a
[root@db-192-168-173-219 ~]# zpool status -v
  pool: zp1
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Thu Jul 31 08:31:53 2014
    3.41G scanned out of 8.62T at 17.4M/s, 144h42m to go
    300M resilvered, 0.04% done
config:

        NAME                                            STATE     READ WRITE CKSUM
        zp1                                             DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            sdb                                         ONLINE       0     0     0
            sdc                                         ONLINE       0     0     0
            sdd                                         ONLINE       0     0     0
            sde                                         ONLINE       0     0     0
            sdf                                         ONLINE       0     0     0
            sdg                                         ONLINE       0     0     0
            sdh                                         ONLINE       0     0     0
            sdi                                         ONLINE       0     0     0
            sdj                                         ONLINE       0     0     0
            sdk                                         ONLINE       0     0     0
            spare-10                                    FAULTED      0     0     0
              sdl                                       FAULTED     11   586     0  too many errors
              scsi-36c81f660eb18e8001b32c5c61a48318a    ONLINE       0     0     0  (resilvering)
        logs
          scsi-36c81f660eb18e8001af8e4ec0420e21f-part4  ONLINE       0     0     0
        spares
          scsi-36c81f660eb18e8001b32c5c61a48318a        INUSE     currently in use

errors: No known data errors

resilver的时间, 和扫描速度, 以及ZPOOL已使用的空间有关, 我们看到的这个例子, 已经使用的空间有8.62T, 扫描速度只有17.4M/s, 所以评估需要144小时42分钟.
 
 scan: resilver in progress since Thu Jul 31 08:31:53 2014
    3.41G scanned out of 8.62T at 17.4M/s, 144h42m to go
    300M resilvered, 0.04% done


如果有硬盘更换上去, 在更换前, 最好先把硬盘改成offline的.
 
[root@db-192-168-173-219 test1]# zpool offline zp1 sdl
[root@db-192-168-173-219 opt]# zpool status -v zp1
  pool: zp1
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Thu Jul 31 09:43:21 2014
    246M scanned out of 8.63T at 12.3M/s, 204h27m to go
    22.1M resilvered, 0.00% done
config:

        NAME                                            STATE     READ WRITE CKSUM
        zp1                                             DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            sdb                                         ONLINE       0     0     0
            sdc                                         ONLINE       0     0     0
            sdd                                         ONLINE       0     0     0
            sde                                         ONLINE       0     0     0
            sdf                                         ONLINE       0     0     0
            sdg                                         ONLINE       0     0     0
            sdh                                         ONLINE       0     0     0
            sdi                                         ONLINE       0     0     0
            sdj                                         ONLINE       0     0     0
            sdk                                         ONLINE       0     0     0
            spare-10                                    DEGRADED     0     0     0
              sdl                                       OFFLINE     11   586     0
              scsi-36c81f660eb18e8001b32c5c61a48318a    ONLINE       0     0     0  (resilvering)
        logs
          scsi-36c81f660eb18e8001af8e4ec0420e21f-part4  ONLINE       0     0     0
        spares
          scsi-36c81f660eb18e8001b32c5c61a48318a        INUSE     currently in use

errors: No known data errors

然后更换硬盘, 更换好后, 使用replace, 将spare盘释放出来.
 
zpool replace zp1 sdl sdl

硬盘非常大, 所以resilvering过程很漫长, 从zpool status -v可以看到还需要多长时间.
更换过程如下 : 
[root@digoal ~]# MegaCli -CfgLdAdd -r0 [32:10] WB Direct -a0
                                     

Adapter 0: Configure Adapter Failed

FW error description: 
  The current operation is not allowed because the controller has data in cache for offline or missing virtual drives.  

Exit Code: 0x54

[root@digoal ~]# MegaCli -GetPreservedCacheList -aALL
                                     
Adapter #0

Virtual Drive(Target ID 11): Missing.

Exit Code: 0x00
[root@digoal ~]# MegaCli -DiscardPreservedCache -L11 -a0
                                     
Adapter #0

Virtual Drive(Target ID 11): Preserved Cache Data Cleared.

Exit Code: 0x00
[root@digoal ~]# MegaCli -CfgLdAdd -r0 [32:10] WT Direct -a0
                                     
Adapter 0: Created VD 11

Adapter 0: Configured the Adapter!!

Exit Code: 0x00

[root@digoal ~]# zpool replace zp1 /dev/sdl /dev/sdl
invalid vdev specification
use '-f' to override the following errors:
/dev/sdl does not contain an EFI label but it may contain partition
information in the MBR.
[root@digoal ~]# zpool replace -f zp1 /dev/sdl /dev/sdl
[root@digoal ~]# zpool status -v
  pool: zp1
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Tue Aug  5 15:47:35 2014
    100M scanned out of 9.45T at 16.7M/s, 165h6m to go
    9.08M resilvered, 0.00% done
config:

        NAME                                            STATE     READ WRITE CKSUM
        zp1                                             DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            sdb                                         ONLINE       0     0     0
            sdc                                         ONLINE       0     0     0
            sdd                                         ONLINE       0     0     0
            sde                                         ONLINE       0     0     0
            sdf                                         ONLINE       0     0     0
            sdg                                         ONLINE       0     0     0
            sdh                                         ONLINE       0     0     0
            sdi                                         ONLINE       0     0     0
            sdj                                         ONLINE       0     0     0
            sdk                                         ONLINE       0     0     0
            spare-10                                    DEGRADED     0     0     0
              replacing-0                               OFFLINE      0     0     0
                old                                     OFFLINE     11   586     0
                sdl                                     ONLINE       0     0     0  (resilvering)
              scsi-36c81f660eb18e8001b32c5c61a48318a    ONLINE       0     0     0
        logs
          scsi-36c81f660eb18e8001af8e4ec0420e21f-part4  ONLINE       0     0     0
        spares
          scsi-36c81f660eb18e8001b32c5c61a48318a        INUSE     currently in use

errors: No known data errors


接下来模拟一下整个的过程, offline一个盘, 使用hot spare顶上去, 更换硬盘, 将更换后的硬盘顶替坏盘, hot spare盘自动释放回hot spare avail状态.
创建3个文件. 
# dd if=/dev/zero of=/opt/zfs.disk1 bs=8192 count=102400
# dd if=/dev/zero of=/opt/zfs.disk2 bs=8192 count=102400
# dd if=/dev/zero of=/opt/zfs.disk3 bs=8192 count=102400

创建zpool
 
[root@db-192-168-173-219 opt]# zpool create -o ashift=12 -o autoreplace=off zp2 mirror /opt/zfs.disk1 /opt/zfs.disk2 spare /opt/zfs.disk3

查看当前状态
 
[root@db-192-168-173-219 opt]# zpool status zp2
  pool: zp2
 state: ONLINE
  scan: none requested
config:

        NAME                STATE     READ WRITE CKSUM
        zp2                 ONLINE       0     0     0
          mirror-0          ONLINE       0     0     0
            /opt/zfs.disk1  ONLINE       0     0     0
            /opt/zfs.disk2  ONLINE       0     0     0
        spares
          /opt/zfs.disk3    AVAIL   

errors: No known data errors

手工offline一块盘.
 
[root@db-192-168-173-219 opt]# zpool offline zp2 /opt/zfs.disk1

查看当前状态
 
[root@db-192-168-173-219 test1]# zpool status -v zp2
  pool: zp2
 state: DEGRADED
status: One or more devices has been taken offline by the administrator.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Online the device using 'zpool online' or replace the device with
        'zpool replace'.
  scan: scrub repaired 0 in 0h0m with 0 errors on Thu Jul 31 09:20:25 2014
config:

        NAME                STATE     READ WRITE CKSUM
        zp2                 DEGRADED     0     0     0
          mirror-0          DEGRADED     0     0     0
            /opt/zfs.disk1  OFFLINE      0     0     0
            /opt/zfs.disk2  ONLINE       0     0     0
        spares
          /opt/zfs.disk3    AVAIL   

errors: No known data errors

使用hot spare盘顶替offline的盘.
 
[root@db-192-168-173-219 opt]# zpool replace zp2 /opt/zfs.disk1 /opt/zfs.disk3
[root@db-192-168-173-219 opt]# zpool status zp2
  pool: zp2
 state: DEGRADED
status: One or more devices has been taken offline by the administrator.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Online the device using 'zpool online' or replace the device with
        'zpool replace'.
  scan: resilvered 1000K in 0h0m with 0 errors on Thu Jul 31 09:26:25 2014
config:

        NAME                  STATE     READ WRITE CKSUM
        zp2                   DEGRADED     0     0     0
          mirror-0            DEGRADED     0     0     0
            spare-0           OFFLINE      0     0     0
              /opt/zfs.disk1  OFFLINE      0     0     0
              /opt/zfs.disk3  ONLINE       0     0     0
            /opt/zfs.disk2    ONLINE       0     0     0
        spares
          /opt/zfs.disk3      INUSE     currently in use

接下来直接使用原盘替换时会报错, 因为这个盘目前有zpool的信息. 起到了保护作用.
 
[root@db-192-168-173-219 test1]# zpool replace zp2 /opt/zfs.disk1 /opt/zfs.disk1
invalid vdev specification
use '-f' to override the following errors:
/opt/zfs.disk1 is part of active pool 'zp2'

删除原盘对应的文件, 并新建一个文件来顶替
 
[root@db-192-168-173-219 opt]# rm -f zfs.disk1
[root@db-192-168-173-219 opt]# zpool replace zp2 /opt/zfs.disk1 /opt/zfs.disk1
cannot resolve path '/opt/zfs.disk1'
[root@db-192-168-173-219 opt]# dd if=/dev/zero of=/opt/zfs.disk1 bs=8192 count=102400 
102400+0 records in
102400+0 records out
838860800 bytes (839 MB) copied, 1.48687 s, 564 MB/s

使用新建的文件定义offline的盘. hot spare盘回到avail状态.
 
[root@db-192-168-173-219 opt]# zpool replace zp2 /opt/zfs.disk1 /opt/zfs.disk1
[root@db-192-168-173-219 opt]# zpool status -v zp2
  pool: zp2
 state: ONLINE
  scan: resilvered 1.05M in 0h0m with 0 errors on Thu Jul 31 09:27:28 2014
config:

        NAME                STATE     READ WRITE CKSUM
        zp2                 ONLINE       0     0     0
          mirror-0          ONLINE       0     0     0
            /opt/zfs.disk1  ONLINE       0     0     0
            /opt/zfs.disk2  ONLINE       0     0     0
        spares
          /opt/zfs.disk3    AVAIL   

errors: No known data errors


[注意]
1. zpool的autoreplace和hot spare没有关系, 只和原盘有关, 当原盘被一个新的盘插入时自动加入原盘所在的vdev. 
       autoreplace=on | off

           Controls automatic device replacement. If set to "off", device replacement must be initiated by the  admin-
           istrator  by  using the "zpool replace" command. If set to "on", any new device, found in the same physical
           location as a device that previously belonged to the pool, is automatically  formatted  and  replaced.  The
           default behavior is "off". This property can also be referred to by its shortened column name, "replace".

2.  从下面的exp来看, 如果hot spare处于resilvering状态, 最好等resilver结束再replace到更换后的盘.
 
       zpool scrub [-s] pool ...

           Begins  a  scrub. The scrub examines all data in the specified pools to verify that it checksums correctly.
           For replicated (mirror or raidz) devices, ZFS automatically repairs any damage discovered during the scrub.
           The  "zpool  status" command reports the progress of the scrub and summarizes the results of the scrub upon
           completion.

           Scrubbing and resilvering are very similar operations. The difference is  that  resilvering  only  examines
           data that ZFS knows to be out of date (for example, when attaching a new device to a mirror or replacing an
           existing device), whereas scrubbing examines all data to discover silent errors due to hardware  faults  or
           disk failure.

           Because  scrubbing  and resilvering are I/O-intensive operations, ZFS only allows one at a time. If a scrub
           is already in progress, the "zpool scrub" command terminates it and starts a new scrub. If a resilver is in
           progress, ZFS does not allow a scrub to be started until the resilver completes.

           -s    Stop scrubbing.
       Example 11 Managing Hot Spares

       The following command creates a new pool with an available hot spare:

         # zpool create tank mirror sda sdb spare sdc

       If one of the disks were to fail, the pool would be reduced to the degraded state. The  failed  device  can  be
       replaced using the following command:

         # zpool replace tank sda sdd

       Once  the  data  has  been  resilvered, the spare is automatically removed and is made available for use should
       another device fails. The hot spare can be permanently removed from the pool using the following command:

         # zpool remove tank sdc


[参考]
weixin_34221773
关注
【Android】adb devices 出现devices offline的问题
静谧、淡雅
08-20 878
adb devices 出现devices offline的问题
Android studio找不到设备，adb.exe:device offline
码点
09-01 3072
Android studio找不到设备，adb.exe:device offline 在做Android开发时经常出现android adb devices offline，解决办法如下： 1 重启adb服务 adb kill-server adb start-server linux下别忘了以root身份运行 2 上一步无效的情况下，将手机USB调试关闭后再次打开，重新执行上一步 3 仍旧不行的话，重启手机 4 到这步不行的话只能重启电脑了 5 有时候是数据线的问题，需要换一根数据线就好了 ...
修复zpool data errors错误
weixin_34247155的博客
04-17 1711
故障信息：root@host1:/tank/new/ddd# zpool status -v tank pool: tank state: ONLINEstatus: One or more devices has experienced an error resulting in data corruption. Applications may be a...
zfs 存储池无法挂载解决方案
qq_14915781的博客
07-18 4640
bash-4.1# zpool import -d /dev/disk/by-id pool: data id: 16015589977926012805 state: FAULTED status: The pool metadata is corrupted. action: The pool cannot be imported due to damaged devices or ...
Linux学习之文件系统zfs文件系统之zpool命令详解
热门推荐
马哥私房菜
06-29 1万+
ZPOOL(8) System Manager's Manual ZPOOL(8) NAME zpool — configure ZFS storage pools SYNOPSIS zpool -? zpool.
PVE zfs替换UNAVAIL的硬盘
DONG999的专栏
10-26 1426
ls -la /dev/disk/by-id #查看新硬盘id zpool replace mypool /dev/disk/by-id/旧硬盘id /dev/disk/by-id/新硬盘id zpool offline mypool /dev/disk/by-id/旧硬盘id zpool detatch mypool /dev/disk/by-id/旧硬盘id
服务器zfs文件系统修复过程记录
beiya123的博客
09-17 822
一、服务器数据恢复介绍： 一台zfs文件系统的服务器，配备32块硬盘，Windows操作系统。 二、服务器数据恢复故障情况 设备在运行过程中突然崩溃，设备不存在物理故障，重启后问题没有解决，需要恢复服务器内的大量数据。 三、备份服务器数据 北亚数据恢复工程师第客户服务器进行扇区级镜像操作，通过对镜像文件分析获取到如下信息： zfs文件系统 服务器硬盘共分4组 热备盘全部启用 四、服务器故障情况分析 故障服务器4组raidz里有两组中的热备盘启动了，其中第一组启用了一块热备盘，第二组启用了3块。
解决adb error: device offline也包含4.2.2版本fastboot
03-11
然而，有时我们可能会遇到“device offline”的错误提示，这通常意味着ADB无法识别或连接到设备。本篇将详细介绍如何解决“adb error: device offline”问题，并重点讨论在Android 4.2.2版本下使用ADB及Fastboot工具...
DELL服务器启动报错there are offline or missing virtual drivers with preserved cache
网络管理员
08-25 5306
生产一台服务器硬盘故障报错，关机拔出硬盘装入新硬盘，启动要进入阵列卡系统，启动无法进入，报错 There are offline or missing virtual drives with preserved cache. Please check the cables and ensure that all drives are present. Press any key to enter the configuration utility. 无法进入系统。 解决办法如下: 进入raid管理，F2，编
oracle存储换故障硬盘,更换或修复损坏的设备
weixin_29373959的博客
04-14 1135
更换或修复损坏的设备本节介绍如何确定设备故障类型、清除瞬态错误和替换设备。确定设备故障的类型术语损坏的设备相当含糊，它可以用来描述许多可能的情况：位损坏－随着时间的推移，随机事件(如电磁感应和宇宙射线)可能会导致存储在磁盘上的位发生翻转。这些事件相对少见，但是通常足以导致大系统或长时间运行的系统出现潜在的数据损坏。误导的读取或写入－固件已知问题或硬件故障可以导致整个块的读取或写入引用磁盘上的不正确...
centos5.5 raid1出现问题然后重新同步
weixin_34220834的博客
11-22 669
今天进入系统检查了一下raid1的状态发现degraded了，因为做了raid1 samba还是可以访问的。所以打开机箱检查了一下硬盘连接线重新插拔了一下电源线 post自检检查到另一块硬盘。 1.[root@zh888 ~]# mdadm -D /dev/md0 /dev/md0: Version : 0.90 Creatio...
问题解决：Too many errors! 3 errors were dropped
开发游戏的老王
01-02 3777
错误信息 运行时报错 E 0:00:00:0666 Too many errors! 3 errors were dropped. <C Source> :32 解决办法 Godot Editor因为性能的原因对每一帧警告信息显示数量有限制 可以在项目->项目设置->常规->Network->Debugger Stdout中将Max Erro...
【服务器数据恢复】多块磁盘离线导致RAIDZ崩溃的数据恢复案例
beiya123的博客
02-20 471
服务器数据恢复环境： SUN ZFS系列某型号存储阵列； 40块磁盘组建的存储池（其中4块磁盘用作全局热备盘），池内划分出若干空间映射到服务器使用； 服务器使用Windows操作系统。 服务器故障： 服务器在工作时由于未知原因崩溃，排除断电、进水或者误操作等外部因素。管理员重启服务器后发现无法进入系统，需要恢复该存储内的所有数据。
ZFS命令学习
自卸式运砖卡车司机
08-06 5681
建立删除卷 1 2 3 4 5 6 [root@cahesi ~] zpool create testzpool raidz -f vda vdb [root@cahesi ~]# zpool list NAME        SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP...
zpool import 找不到存储池
每天的表现，未来的必然！
10-26 4764
在使用zfs文件系统的时候，有时候发现export存储池A后，zpool import并不能找到刚export的存储池A，这种情况下，zpool import A存储池是会失败的，如果用zpool create -f A /dev/sdb1重新创建A存储池，那么A存储池export之前的东西就都丢失了，这不是我们想要的。google一番，最后找到了解决方法：$ zpool import # 该
oracle dg 至少几块盘,oracle dg 报错提示 涉及硬盘错误
weixin_29443363的博客
04-08 131
###oracle dg 报错提示 涉及硬盘错误Dec 23 03:28:01 xhisdg rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="4554" x-info="http://www.rsyslog.com"] rsyslogd was HUPedDec 23 03:28:03 xhisdg rhsmd: In...
zpool add top-level vdev; attach, detach, offline, online, replace vdev;
weixin_33724659的博客
04-05 703
zpool允许我们动态的添加vdev, 这个我们已经在上一篇BLOG中介绍过. http://blog.163.com/digoal@126/blog/static/163877040201442731413803/ 如添加spare[root@db-172-16-3-150 ssd1]# zpool add zpp spare /ssd1/zfs.6 ...
linux系统启动VCS失败,过期文件导致VCS双机启动失败
weixin_29846499的博客
05-01 521
现场环境：SUSE9SP3linux +VCS4.1MP4双机问题描述：启动VCS双机报错#hastartdNFS_Disksurp9fs3 *FAULTED*groupresource system message--------------- -------------------- ----------------...
adb device offline
最新发布
03-16
adb device offline表示设备与计算机失去连接，无法进行调试或文件传输等操作。可能的原因包括设备未启用USB调试模式、USB连接线松动或损坏、驱动程序未正确安装等。解决方法包括重新插拔USB连接线、重启设备和计算机、更新驱动程序等。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值