On Sunday, October 04, 2015 11:41:44 PM Moby wrote:

On 10/04/2015 10:36 PM, Andrei Borzenkov wrote:

...

05.10.2015 01:31, Patrick Shanahan пишет:

...

While the dl took quite some time, all five local machine appear quite well, only one noticed hickup. Acer laptop with Radeon HD 8650G card displays some odd ascii characters centered rather than the green splash screen when moving from runlevel 3 to 5.

I also got the same funny looking characters after reboot. Usually it is indication that console was not properly setup (no font loaded).

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Regards,

Assume I see the same message. It is only shown just after the reboot and the message is to fast to read it complete. In the boot.log file this message is not shown. -- Linux User 183145 using KDE4 Tumbleweed on a Pentium IV , powered by openSUSE 20151002 (x86_64) Kernel: 4.2.3-1.gef1562d-default KDE Development Platform: 4.14.10 12:21pm up 0:07, 1 user, load average: 0.46, 1.79, 1.14 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Ditto. I saw them too after rebooting.

Am Montag, 5. Oktober 2015, 11:02:51 schrieb Andrei Borzenkov:

On Mon, Oct 5, 2015 at 7:41 AM, Moby wrote:

...

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

From quick glance over dracut package, it unconditionally adds /sysroot to initrd's /etc/fstab in patch 0400-use_fstab_systemd.patch. Small nitpick: It doesn't add it during boot, it's already in the initrd: lsinitrd /boot/initrd /etc/fstab

But systemd generates /sysroot mount from root= kernel command line already. So we get duplicate indeed. Correct! The patch is a simplification of the dracut root "stuff", as with all modules and systemd together it has become quite a mess. The responsibility of deciding between "root=" and /etc/fstab is moved out from dracut into systemd-fstab-generator, where is is implemented already, but not used yet. This resulted in code duplication and even more mess...

I'm not sure what this patch intended to fix, because its subject directly contradicts single line comment :) It doesn't fix anything directly, but in the long run it's intended to get rid of "root=" in the default grub config. The "root=" parameter is still fully supported, of course, but right now there is an issue with handling of mount options on /. If "root=<something>" is given on the kernel command line, the initrd ignores the entry for / in /etc/fstab completely. That's basically why the warning is there, although fairly generic. The issue with this is, that should there be any special mount options that can not be applied with "mount -o remount", those options will never have any effect whatsoever. Another parameter "rootflags=" is for suppling options that go together with "root=", but it's not set automatically.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Montag, 5. Oktober 2015, 11:43:10 schrieb Andrei Borzenkov:

On Mon, Oct 5, 2015 at 11:34 AM, Fabian wrote:

...

Am Montag, 5. Oktober 2015, 11:02:51 schrieb Andrei Borzenkov:

...

On Mon, Oct 5, 2015 at 7:41 AM, Moby wrote:

...

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

From quick glance over dracut package, it unconditionally adds /sysroot to initrd's /etc/fstab in patch 0400-use_fstab_systemd.patch. Small nitpick: It doesn't add it during boot, it's already in the initrd: lsinitrd /boot/initrd /etc/fstab

I did not say "adds /etc/fstab". I said "adds TO /etc/fstab". By "it" I meant the entry for /sysroot.

...

...

But systemd generates /sysroot mount from root= kernel command line already. So we get duplicate indeed. Correct! The patch is a simplification of the dracut root "stuff", as with all modules and systemd together it has become quite a mess. The responsibility of deciding between "root=" and /etc/fstab is moved out from dracut into systemd-fstab-generator,

Really? Could you point to source? systemd-fstab-generator generates /sysroot mount from root= kernel command line; it does not use any fstab for it. At least, in upstream ... First is parses /proc/cmdline for /sysroot and /sysroot/usr, then it parses /etc/fstab (and /sysroot/etc/fstab). If there was no "root=" entry in /proc/cmdline (we want to get rid of it by default), systemd-fstab-generator could not generate sysroot.mount, so /sysroot is now in /etc/fstab, unconditionally. Before the patch, there would still be a "root=", but in the initrd's /etc/cmdline.d/, which is a dracut-only thing and systemd-fstab-generator doesn't know about that, so the functionality of systemd-fstab-generator had to be implemented in dracut as well to allow booting without "root=".

(It's a similiar issue with cryptsetup (the rd.luks.key bug, for example), where code in systemd is implemented in dracut as well, but both have entirely different semantics, so the solution is to decide which of those to use. For crypt it's fairly easy, dracut itself implements more features, like rd.luks.key, but for "root=", it's different again)

...

where is is implemented already, but not used yet. This resulted in code duplication and even more mess...

...

I'm not sure what this patch intended to fix, because its subject directly contradicts single line comment :) It doesn't fix anything directly, but in the long run it's intended to get rid of "root=" in the default grub config. The "root=" parameter is still fully supported, of course, but right now there is an issue with handling of mount options on /. If "root=<something>" is given on the kernel command line, the initrd ignores the entry for / in /etc/fstab completely. That's basically why the warning is there, although fairly generic. The issue with this is, that should there be any special mount options that can not be applied with "mount -o remount", those options will never have any effect whatsoever. Another parameter "rootflags=" is for suppling options that go together with "root=", but it's not set automatically.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/10/15 05:41, Moby wrote:

On 10/04/2015 10:36 PM, Andrei Borzenkov wrote:

...

05.10.2015 01:31, Patrick Shanahan пишет:

...

While the dl took quite some time, all five local machine appear quite well, only one noticed hickup. Acer laptop with Radeon HD 8650G card displays some odd ascii characters centered rather than the green splash screen when moving from runlevel 3 to 5. I also got the same funny looking characters after reboot. Usually it is indication that console was not properly setup (no font loaded).

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Regards,

I see this on one of my boxes, no duplicate entry exists in /etc/fstab. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Sid Boyce [10-05-15 11:04]:

On 05/10/15 15:51, Sid Boyce wrote:

...

On 05/10/15 05:41, Moby wrote:

...

On 10/04/2015 10:36 PM, Andrei Borzenkov wrote:

...

05.10.2015 01:31, Patrick Shanahan пишет:

...

While the dl took quite some time, all five local machine appear quite well, only one noticed hickup. Acer laptop with Radeon HD 8650G card displays some odd ascii characters centered rather than the green splash screen when moving from runlevel 3 to 5. I also got the same funny looking characters after reboot. Usually it is indication that console was not properly setup (no font loaded).

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Regards,

I see this on one of my boxes, no duplicate entry exists in /etc/fstab. Regards Sid.

Sorry, on all my boxes in fact - looking at journalctl -b.

And I see it on none of mine. Do you use "zypper dup"?

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Fabian [10-05-15 12:25]:

Am Montag, 5. Oktober 2015, 12:17:51 schrieb Patrick Shanahan:

...

* Sid Boyce [10-05-15 11:04]:

...

On 05/10/15 15:51, Sid Boyce wrote:

...

On 05/10/15 05:41, Moby wrote:

...

On 10/04/2015 10:36 PM, Andrei Borzenkov wrote:

...

05.10.2015 01:31, Patrick Shanahan пишет: >While the dl took quite some time, all five local machine appear quite >well, only one noticed hickup. Acer laptop with Radeon HD 8650G card >displays some odd ascii characters centered rather than the green >splash >screen when moving from runlevel 3 to 5. I also got the same funny looking characters after reboot. Usually it is indication that console was not properly setup (no font loaded).

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Regards,

I see this on one of my boxes, no duplicate entry exists in /etc/fstab. You'll understand why if you read the bug report (https://bugzilla.opensuse.org/show_bug.cgi?id=948771) or my posts to this list.

...

...

...

Regards Sid.

Sorry, on all my boxes in fact - looking at journalctl -b.

And I see it on none of mine. Do you use "zypper dup"? It's only visible if a new initrd was generated, which is normally the case if the kernel was updated.

But kernel was updated and I did *not* see the err. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Andrei Borzenkov [10-05-15 14:01]:

05.10.2015 19:17, Patrick Shanahan пишет: [...]

...

And I see it on none of mine.

Do you have root=xxx on kernel command line?

no, should I. Don't recall ever having it. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Knurpht - Gertjan Lettink [10-05-15 17:30]:

Op Monday 05 October 2015 16:01:59 schreef Patrick Shanahan:

...

* Andrei Borzenkov [10-05-15 14:01]:

...

05.10.2015 19:17, Patrick Shanahan пишет: [...]

...

...

And I see it on none of mine.

Do you have root=xxx on kernel command line?

no, should I. Don't recall ever having it.

That's weird. What does your /boot/grub2/grub.cfg look like?

http://wahoo.no-ip.org/~pat/grub.cfg -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/10/15 17:17, Patrick Shanahan wrote:

* Sid Boyce [10-05-15 11:04]:

...

On 05/10/15 15:51, Sid Boyce wrote:

...

On 05/10/15 05:41, Moby wrote:

...

On 10/04/2015 10:36 PM, Andrei Borzenkov wrote:

...

05.10.2015 01:31, Patrick Shanahan пишет:

...

While the dl took quite some time, all five local machine appear quite well, only one noticed hickup. Acer laptop with Radeon HD 8650G card displays some odd ascii characters centered rather than the green splash screen when moving from runlevel 3 to 5. I also got the same funny looking characters after reboot. Usually it is indication that console was not properly setup (no font loaded).

After applying this update to two different (one 64 and other 32 bit) machines, I get the following error displayed during boot:

systemd-fstab-generator[95]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Anyone else seeing this?

Regards,

I see this on one of my boxes, no duplicate entry exists in /etc/fstab. Regards Sid.

Sorry, on all my boxes in fact - looking at journalctl -b. And I see it on none of mine. Do you use "zypper dup"?

...

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org Yes, I use zypper dup. Regards Sid.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org