Hello, I have an f18 setup with all-in-one ovirt nightly. The system has two disks /dev/sda and /dev/sdb I notice that in ovirt seup a multipath.conf file has been written: # RHEV REVISION 0.9 defaults { polling_interval 5 getuid_callout "/lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/%n" no_path_retry fail user_friendly_names no flush_on_last_del yes fast_io_fail_tmo 5 dev_loss_tmo 30 max_fds 4096 } devices { device { vendor "HITACHI" product "DF.*" getuid_callout "/lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/%n" } device { vendor "COMPELNT" product "Compellent Vol" no_path_retry fail } } I get many of these errors in messages Jan 10 23:48:39 tekkaman kernel: [ 7903.668803] device-mapper: table: 253:2: multipath: error getting device Jan 10 23:48:39 tekkaman kernel: [ 7903.668812] device-mapper: ioctl: error adding target to table Jan 10 23:48:39 tekkaman kernel: [ 7903.672479] device-mapper: table: 253:2: multipath: error getting device Jan 10 23:48:39 tekkaman kernel: [ 7903.672488] device-mapper: ioctl: error adding target to table Jan 10 23:48:39 tekkaman kernel: [ 7903.675306] device-mapper: table: 253:2: multipath: error getting device Jan 10 23:48:39 tekkaman kernel: [ 7903.675315] device-mapper: ioctl: error adding target to table Jan 10 23:48:39 tekkaman kernel: [ 7903.678268] device-mapper: table: 253:2: multipath: error getting device Jan 10 23:48:39 tekkaman kernel: [ 7903.678276] device-mapper: ioctl: error adding target to table Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Jan 10 23:48:39 tekkaman multipathd: dm-2: remove map (uevent) Could the be related? $ sudo multipath -l Jan 10 23:49:27 | multipath.conf +5, invalid keyword: getuid_callout Jan 10 23:49:27 | multipath.conf +18, invalid keyword: getuid_callout Is this necessary for my internal disks or not? Otherwise from [g.cecchi@tekkaman ~]$ sudo /lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/sda 35002538043584d30 [g.cecchi@tekkaman ~]$ sudo /lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/sdb 35000cca313d8b629 I would put this in my multipath.conf: blacklist { wwid 35002538043584 wwid 35000cca313d8b629 } Thanks, Gianluca