Comment # 6 on bug 1106005 from Markus Zimmermann

Thanks for looking into this.

- `service multipathd status` tells me that this service is inactive since
about two weeks. Which is interesting since the crash on this device did not
happen this weekend but the weekend before that.

- `multipath -ll` gives the following output:

```
eui.00080d02001b6dd8 dm-0 NVME,THNSN5512GPU7 TOSHIBA                   
size=477G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  `- 0:0:1:1 nvme0n1 259:0 active ready running
eui.00080d02001b6e33 dm-1 NVME,THNSN5512GPU7 TOSHIBA                   
size=477G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  `- 1:0:1:1 nvme1n1 259:1 active ready running
```

- `dmsetup ls --tree`

```
eui.00080d02001b6e33-part3 (254:7)
 ������eui.00080d02001b6e33 (254:1)
    ������ (259:1)
eui.00080d02001b6e33-part2 (254:6)
 ������eui.00080d02001b6e33 (254:1)
    ������ (259:1)
eui.00080d02001b6e33-part1 (254:5)
 ������eui.00080d02001b6e33 (254:1)
    ������ (259:1)
eui.00080d02001b6dd8-part3 (254:4)
 ������eui.00080d02001b6dd8 (254:0)
    ������ (259:0)
eui.00080d02001b6dd8-part2 (254:3)
 ������eui.00080d02001b6dd8 (254:0)
    ������ (259:0)
eui.00080d02001b6dd8-part1 (254:2)
 ������eui.00080d02001b6dd8 (254:0)
    ������ (259:0)
```

Was this the information you were looking for?