13.01.2016 11:46, Felix Miata пишет:
Andrei Borzenkov composed on 2016-01-13 10:44 (UTC+0300):
Felix Miata composed:
Or to put it differently - how you determine whether initrd was built using hostonly mode?
Examine the timestamps: http://fm.no-ip.com/Tmp/SUSE/Factory/
This is the dracut.conf file in place prior to the day's zypper update: http://fm.no-ip.com/Tmp/SUSE/Factory/dracut.conf.07
Note it contains hostonly="no" uncommented.
/etc/dracut.conf.d takes precedence and sets hostonly=yes so this line should have no effect.
Then what made the initrd 4X typical size?
I do not know. I do not see any difference in generated initrd whether or not I use "hostonly=no" in /etc/dracut.conf.
@Felix: do you have /etc/multipath.conf on your system? Do you have it in initrd that exhibits this problem? Could you show content of both?
/etc/multipath.conf does not exist. Grepping multipath in lsinitrd output produces no results in the /etc/ tree.
Could you send "journalctl -b" when booting with "bad" initrd?
OK, this is yet another difference between traditional and systemd-enabled dracut - systemd service does not check for/etc/multipath.conf and always starts multipathd. You can suppress multipath using rd.multipath=0 (or nompath which should also affect normal system). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org