Andrei Borzenkov composed on 2016-01-13 06:28 (UTC+0300):
Felix Miata composed:
Andrei Borzenkov composed on 2016-01-12 23:11 (UTC+0300):
Felix Miata composed:
With current TW's 4.3.3 it's more verbose: Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/Hitachi_HCS5C1050CLA382_JC0550HV2DJZTH-part23 5655815 5055450 309512 95% / ...
Anyway, could you show "dmsetup status"?
Hitachi_HCS5C1050CLA382_JC0550HV2DJZTH: 0 976773168 multipath 2 0 0 0 1 1 A 0 1 2 8:0 A 0 0 1
So your system decided to use multipath for disk.
Looks to me like Stefan's response was on the right track.
I remember similar question on forums. I do not think it really depends on kernel version, because kernel does not create those mappings by itself. For some reasons multipath got added to initrd when it was rebuilt for new kernel.
You could try to boot from live media and recreate initrd;
Should I want to after already having built second initrd (via chroot) that hasn't the problem?
I'm afraid that doing it from live system now would pick up multipath again.
The 36562K initial initrd was built on its initial installation with dracut configured with hostonly=yes. When I rebuilt it after changing dracut configuration to hostonly=no, and adddriver changes, the quicker booting 9437K result uses the traditional short names. I don't see any point building same initrd a third time. I have now set it immutable, so we shall see what happens on installing the next kernel that comes along, hopefully soon now that 4.4 is past RC. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org