Dispositivos de bloco SCSI FibreChannel-SAN se perdem

1

Existem 3 LUNs em um FC-SAN que desejo acessar usando 2 HBAs (com dois caminhos cada. Quando o sistema é inicializado, tudo parece bem, mas depois de um tempo o sd * -devices do segundo HBA desapareceu e não tenho idéia por que ou como recuperá-los sem reiniciar. A varredura do barramento SCSI ainda encontra todos os dispositivos, mas o kernel não fica ciente dos dispositivos de bloco. É o Red Hat 6.6 com as atualizações mais recentes.

Os mesmos LUNs estão disponíveis em 4 caminhos em outro sistema, mas somente em 2 neste.

Alguém tem alguma idéia do que eu poderia estar perdendo?

# lspci|grep Fibre
08:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)
08:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)


# lsscsi
...
[1:0:0:1]    disk    DataCore Virtual Disk     DCS   /dev/sdb
[1:0:0:2]    disk    DataCore Virtual Disk     DCS   /dev/sdc
[1:0:0:3]    disk    DataCore Virtual Disk     DCS   /dev/sdd
[1:0:1:1]    disk    DataCore Virtual Disk     DCS   /dev/sde
[1:0:1:2]    disk    DataCore Virtual Disk     DCS   /dev/sdf
[1:0:1:3]    disk    DataCore Virtual Disk     DCS   /dev/sdg
[2:0:0:1]    disk    DataCore Virtual Disk     DCS   -
[2:0:0:2]    disk    DataCore Virtual Disk     DCS   -
[2:0:0:3]    disk    DataCore Virtual Disk     DCS   -
[2:0:1:1]    disk    DataCore Virtual Disk     DCS   -
[2:0:1:2]    disk    DataCore Virtual Disk     DCS   -
[2:0:1:3]    disk    DataCore Virtual Disk     DCS   -
...
# rescan-scsi-bus.sh
...
0 new or changed device(s) found.
0 remapped or resized device(s) found.
0 device(s) removed.

Isso foi registrado quando aconteceu:

May 24 12:08:57 hostname  kernel: sd 1:0:0:1: Parameters changed
May 24 12:08:57 hostname  kernel: sd 1:0:1:3: Parameters changed
May 24 12:09:01 hostname  kernel: sd 1:0:1:2: Parameters changed
May 24 12:09:24 hostname  kernel: sd 1:0:1:1: Parameters changed
May 24 12:09:24 hostname  kernel: sd 2:0:0:1: rejecting I/O to offline device
May 24 12:09:25 hostname  multipathd: checker failed path 8:112 in map lun0
May 24 12:09:25 hostname  multipathd: ora_data2: remaining active paths: 3
May 24 12:09:25 hostname  multipathd: checker failed path 8:128 in map lun1
May 24 12:09:25 hostname  multipathd: ora_acfs1: remaining active paths: 3
May 24 12:09:25 hostname  multipathd: checker failed path 8:144 in map lun2
May 24 12:09:25 hostname  multipathd: ora_acfs2: remaining active paths: 3
May 24 12:09:25 hostname  multipathd: checker failed path 8:160 in map lun0
May 24 12:09:25 hostname  multipathd: ora_data2: remaining active paths: 2
May 24 12:09:25 hostname  multipathd: checker failed path 8:176 in map lun1
May 24 12:09:25 hostname  multipathd: ora_acfs1: remaining active paths: 2
May 24 12:09:25 hostname  multipathd: checker failed path 8:192 in map lun2
May 24 12:09:25 hostname  multipathd: ora_acfs2: remaining active paths: 2
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:112.
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:128.
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:144.
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:160.
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:176.
May 24 12:09:25 hostname  kernel: device-mapper: multipath: Failing path 8:192.

Infelizmente, não tenho acesso ao dispositivo SAN, mas me disseram que nada foi tocado.

Acabei de ver que os dispositivos que de fato desapareceram voltaram 2 horas depois:

May 24 14:06:35 hostname kernel: scsi 2:0:1:1: Attached scsi generic sg9 type 0
May 24 14:06:35 hostname kernel: scsi 2:0:1:2: Attached scsi generic sg10 type 0
May 24 14:06:35 hostname kernel: scsi 2:0:1:3: Attached scsi generic sg11 type 0
May 24 14:06:37 hostname kernel: scsi 2:0:0:1: Attached scsi generic sg12 type 0
May 24 14:06:37 hostname kernel: scsi 2:0:0:2: Attached scsi generic sg13 type 0
May 24 14:06:37 hostname kernel: scsi 2:0:0:3: Attached scsi generic sg14 type 0

É possível que o interruptor FC entre desligado tenha sido desligado nesse tempo. Quando o sistema inicializou anteriormente e os dispositivos sd foram criados como de costume, a linha difere ligeiramente:

May 24 11:14:15 hostname kernel: sd 2:0:1:3: Attached scsi generic sg14 type 0

vs.

May 24 14:06:35 hostname kernel: scsi 2:0:1:1: Attached scsi generic sg9 type 0

Diz "scsi" em vez de "sd".

    
por Christian 25.05.2016 / 11:48

0 respostas