mpath target deve ser = 1.5.0 para ter suporte para 'retain_attached_hw_handler'. Este recurso será desativado

0

Eu tenho problemas ao tentar recarregar alguns dispositivos multipathed após atualizar um servidor linux. de alguma forma, os metadevices mudaram de / dev / md1 para / dev / md127.

então eu tenho esses problemas:

# multipath -v 2 -r
May 15 15:22:57 | mpath target must be >= 1.5.0 to have support for 'retain_attached_hw_handler'. This feature will be disabled
reload: mpathax (36006016011a04200b3becc59edf9c755) undef DGC,VRAID
size=400G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=50 status=undef
| |- 4:0:0:0 sds 65:32 active ready running
| '- 2:0:1:0 sdp 8:240 active ready running
'-+- policy='round-robin 0' prio=10 status=undef
  |- 4:0:1:0 sdt 65:48 active ready running
  '- 2:0:0:0 sdo 8:224 active ready running
May 15 15:22:57 | mpath target must be >= 1.5.0 to have support for 'retain_attached_hw_handler'. This feature will be disabled
May 15 15:22:57 | mpathay: ignoring map
May 15 15:22:57 | mpath target must be >= 1.5.0 to have support for 'retain_attached_hw_handler'. This feature will be disabled
May 15 15:22:57 | mpathay: ignoring map
May 15 15:22:57 | mpath target must be >= 1.5.0 to have support for 'retain_attached_hw_handler'. This feature will be disabled
May 15 15:22:57 | mpathay: ignoring map
May 15 15:22:57 | mpath target must be >= 1.5.0 to have support for 'retain_attached_hw_handler'. This feature will be disabled
May 15 15:22:58 | mpathay: ignoring map

o comando do comando de saída

multipath -v 3 -ll 

está aqui: link

alguma ideia do que poderia ser o problema ... a invasão está atualmente degradada porque os dispositivos desaparecem ou mudaram

mdadm --detail /dev/md127
/dev/md127:
        Version : 1.2
  Creation Time : Thu Sep 28 14:15:13 2017
     Raid Level : raid1
     Array Size : 419299328 (399.88 GiB 429.36 GB)
  Used Dev Size : 419299328 (399.88 GiB 429.36 GB)
   Raid Devices : 2
  Total Devices : 1
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Tue May 15 14:45:46 2018
          State : active, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           Name : endor:1  (local to host endor)
           UUID : 84bf828f:aa052e68:7b948447:4e9abe7e
         Events : 19212

    Number   Major   Minor   RaidDevice State
       0       0        0        0      removed
       1      65       64        1      active sync   /dev/sdu

originalmente nós não criamos este ataque, criamos o seguinte:

mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/mapper/mpathaxp1 /dev/mapper/mpathayp1

então estou perplexo como isso se tornou / dev / 127 com apenas um disco ..

obrigado

    
por danidar 15.05.2018 / 15:34

0 respostas

Tags