Control: severity -1 important That severity was exaggerated. Works fine over here locally, with an LIO target setup.
On Wed, 2019-07-17 at 15:20 +0200, root wrote: > Dear Maintainer, > > * What led up to the situation? > > New Debian 10 Buster fresh installation with HBA cards and disks > arrays > multi-attached ((2 HBA cards, 2 arrays of 12 disks, 4 links) > Disks are all listed correctly in /dev/ or /dev/disk/by-*/ > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > install multipath-tools (and depencies) > write wanted aliases in /etc/multipath.conf (see attached file) > > * What was the outcome of this action? > > tryied 'usual' commands, to apply/refresh configuration: > multipath -F > multipath -r > multipath or systemctl restart multipathd.service > > It doesn't work as expected: 'multipath -v2 -ll' should have shown a > populated devices state map: it's empty. > > /dev/mapper/ is empty. /dev/dm-* are not present. > > /etc/multipath/wwids is not updated/replaced. > Do you not have /etc/multipath/bindings file generated in your case ? A lot has changed lately in how multipath-tools works and you may have to fiddle around with settings. But I have it running fine here on my 2 local setups: sanboot and usual one. > * What outcome did you expect instead? > > Aliases in /dev/mapper/ to use with zfs-dkms. > > Note: > The exact same machine works just fine on Debian 9 Stretch (with zfs- > dkms). > A upgrade to Buster, with untouched /etc/multipath.conf works just > fine also. You mean the same old configuration file from Stretch works fine on Buster ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part