On Thu, Jun 7, 2018 at 4:55 PM femi adegoke <ovirt@fateknollogee.com> wrote:

Noted, regarding your reply about content.

- contents of /etc/multipath.conf

I mean contents of the file /etc/multipath.conf

= conf.d (folder), bindings, wwids

- contents of /etc/multiapth/conf.d/local.conf
blacklist {
wwid INTEL_SSDSCKHB120G4_BTWM65160025120B
devnode "*"

This looks wrong, this is not a valid regular expression. Not sure

what are you trying to do here.

wwid eui.0025385171b04d62
wwid SAMSUNG_MZ7GE960HMHP-000AZ_S1P8NYAG123827

I guess these are sdb and nvme0n1? we see in lsblk?

}

- output of "multipath -ll"
[root@ovirt-node00 ~]# multipath -ll
INTEL_SSDSCKHB120G4_BTWM65160025120B dm-1 ,
size=112G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- #:#:#:# sda 8:0 active undef running

- output "lsblk"
[root@ovirt-node00 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 1G 0 part
├─sda2 8:2 0 110.8G 0 part
└─INTEL_SSDSCKHB120G4_BTWM65160025120B 253:1 0 111.8G 0 mpath
├─INTEL_SSDSCKHB120G4_BTWM65160025120B1 253:2 0 1G 0 part /boot
└─INTEL_SSDSCKHB120G4_BTWM65160025120B2 253:3 0 110.8G 0 part
├─onn_ovirt--node00-swap 253:4 0 11.2G 0 lvm [SWAP]
├─onn_ovirt--node00-pool00_tmeta 253:5 0 1G 0 lvm
│ └─onn_ovirt--node00-pool00-tpool 253:7 0 77.4G 0 lvm
│ ├─onn_ovirt--node00-pool00 253:0 0 77.4G 0 lvm
│ ├─onn_ovirt--node00-ovirt--node--ng--4.2.3.1--0.20180530.0+1 253:8 0 50.4G 0 lvm /
│ ├─onn_ovirt--node00-home 253:10 0 1G 0 lvm /home
│ ├─onn_ovirt--node00-tmp 253:11 0 1G 0 lvm /tmp
│ ├─onn_ovirt--node00-var 253:12 0 15G 0 lvm /var
│ ├─onn_ovirt--node00-var_log 253:13 0 8G 0 lvm /var/log
│ ├─onn_ovirt--node00-var_log_audit 253:14 0 2G 0 lvm /var/log/audit
│ └─onn_ovirt--node00-var_crash 253:16 0 10G 0 lvm /var/crash
└─onn_ovirt--node00-pool00_tdata 253:6 0 77.4G 0 lvm
└─onn_ovirt--node00-pool00-tpool 253:7 0 77.4G 0 lvm
├─onn_ovirt--node00-pool00 253:0 0 77.4G 0 lvm
├─onn_ovirt--node00-ovirt--node--ng--4.2.3.1--0.20180530.0+1 253:8 0 50.4G 0 lvm /
├─onn_ovirt--node00-home 253:10 0 1G 0 lvm /home
├─onn_ovirt--node00-tmp 253:11 0 1G 0 lvm /tmp
├─onn_ovirt--node00-var 253:12 0 15G 0 lvm /var
├─onn_ovirt--node00-var_log 253:13 0 8G 0 lvm /var/log
├─onn_ovirt--node00-var_log_audit 253:14 0 2G 0 lvm /var/log/audit
└─onn_ovirt--node00-var_crash 253:16 0 10G 0 lvm /var/crash
sdb 8:16 0 894.3G 0 disk
nvme0n1 259:0 0 465.8G 0 disk

- output of "lsinitrd"

Based on your next email, looks ok.

Next step:

1. Change the blacklist to:

blacklist {

wwid INTEL_SSDSCKHB120G4_BTWM65160025120B

wwid eui.0025385171b04d62

wwid SAMSUNG_MZ7GE960HMHP-000AZ_S1P8NYAG123827

}

2. Update initrd

dracut --force --add multipath --include /etc/multipath /etc/multipath

3. Reboot

The manual suggest to remove the multiapth device using

multipath -f INTEL_SSDSCKHB120G4_BTWM65160025120B

but I don't think this can work when your root file system

is on top of logical volumes using this device.

If multipath still grabs the device, we will need output of "journalctl -b"

to understand what happened during early boot process.

Nir

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NGN6FNI4RY4NJ3NMP6BK5MAL6IE2GRHM/