On Mon, Oct 5, 2015 at 11:48 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 11:14:20 Andrei Borzenkov wrote:
On Mon, Oct 5, 2015 at 11:05 AM, auxsvr <auxsvr@gmail.com> wrote:
On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active
`- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday,
In which way exactly?
dm-0 turned to dm-2.
it does not matter. Device names are not and never were stable and can change between reboots or even during system uptime (if you remove and then add back the same device).
Perhaps I'm missing something obvious; which part of this output indicates that the device is multipathed?
The very fact that it is output of "multipath -l" command :)
I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device.
??? Number of paths is determined by physical connectivity.
Doesn't this imply that no device is multipathed in my case?
Do not attempt to interpret names. We are speaking about driver that is called "multipath". While its purpose is indeed to work with multiple paths to a single device, this is by no means necessary for the driver to work.
There is no reason for multipath on this system, unless systemd or dracut do something weird.
Sure, systemd is the source of all evil, what else ... so change /etc/fstab to use device-independent mounts (like LABEL or UUID), reboot to verify, disable multipathd.service and multipathd.socket, disable multipath dracut module, recreate initrd and test again. It make sense to rename original initrd before so you have something to manually fall back to.
Actually, I quite like systemd, but I've been bitten by its bugs many times (there's still a bug with logind after restarting dbus that delays logins and spams the system log). multipathd.{service,socket} are disabled,
It is not clear - did you disable them now or they were disabled all the time? Do the run now (systemctl status multipathd.{service,socket})? Remember, "disabled" does not mean "cannot start".
I'll try the rest after some hours, because I need the system at the moment. Also, this[1] and this[2] may be relevant.
-------- [1] http://lists.freedesktop.org/archives/systemd-devel/2014-October/024591.html
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org