On Tue, Jan 8, 2019 at 6:11 PM Ralf Schenk <rs@databay.de> wrote:

Hello,

i see i have already

devices {
    device {
                vendor                 "LIO-ORG"
                hardware_handler       "1 alua"
                features               "1 queue_if_no_path"
                path_grouping_policy   "failover"
                path_selector          "queue-length 0"
                failback               immediate
                path_checker           directio
                #path_checker           tur
                prio                   alua
                prio_args              exclusive_pref_bit
                #fast_io_fail_tmo       25
                no_path_retry          queue
    }
}

Which should result in the same beahaviour, correct ?


Yes, but this is very bad for vdsm if vdsm try to manage such devices.

It is better to put this configuration only for the boot device used by 
the host, and not for any LIO-ORG device.
 

Am 08.01.2019 um 16:48 schrieb Ralf Schenk:

Hello,

I manually renamed them via multipath.conf

multipaths {
    multipath {
        wwid     36001405a26254e2bfd34b179d6e98ba4
        alias    mpath-myhostname-disk1


So here is a better place for

    no_path_retry queue


    }
}

Before I configured multipath (I installed without first before I knew "mpath" parameter in setup !) I had the problem of readonly root a few times but the hints and settings (for iscsid.conf) I found out didn't help. Thats why I had to tweak dracut ramdisk to set up multipath and understand LVM activation and so on of ovirt-ng the hard way.

So you suggest to add 

"no_path_retry queue"
--


Ralf Schenk
fon +49 (0) 24 05 / 40 83 70
fax +49 (0) 24 05 / 40 83 759
mail rs@databay.de
 		 
Databay AG
Jens-Otto-Krag-Straße 11
D-52146 Würselen
www.databay.de

Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns
Aufsichtsratsvorsitzender: Wilhelm Dohmen