Re: Root remaining read-only after boot, no obvious reason why

• Subject: Re: Root remaining read-only after boot, no obvious reason why
• From: Dave Re <Dave.Re@xxxxxxxxxxxxx>
• Date: Tue, 16 May 2023 21:05:46 +0000
• Accept-language: en-US
• Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
• In-reply-to: <ZGPA/ClNFvNqdlpg@kawka3.in.waw.pl>
• Msip_labels:
• References: <CY4PR03MB3141F7CDA1F876B5D2700ECFF7789@CY4PR03MB3141.namprd03.prod.outlook.com> <ZGMnR918ooGcR7GW@kawka3.in.waw.pl> <CY4PR03MB31411D8B075F0EFD89D9FA66F7799@CY4PR03MB3141.namprd03.prod.outlook.com> <ZGOup9X7DDypxEQ+@kawka3.in.waw.pl> <CY4PR03MB31418CE8F02F9E2B4242F88EF7799@CY4PR03MB3141.namprd03.prod.outlook.com> <ZGPA/ClNFvNqdlpg@kawka3.in.waw.pl>

https://freedesktop.org/wiki/Software/systemd/Debugging/ Unfortunately, setting systemd.log_level=debug, and then capturing the full output doesn't expose anything useful. No errors or indications about why systemd-remount-fs.service isn't being run, that I can see. It looks an awful lot like the symptoms called out here https://github.com/systemd/systemd/issues/5358 - but no local-fs.target wants are masked, in my case, so it's not the same.  Prioritize systemd-remount-fs for local-fs.target · Issue #5358 · systemd/systemd Submission type Bug report Request for enhancement (RFE) systemd version the issue has been seen with systemd 232 Used distribution Arch Linux In case of bug report: Expected behaviour you didn't s... github.com Dave Re​ Manager, DevOps Engineering www.imprivata.com 20 CityPoint, 6th Floor ​480 Totten Pond Road ​Waltham, MA  02451 The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.  [ImprivataV12018]

• References:
  • Root remaining read-only after boot, no obvious reason why
    • From: Dave Re
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Dave Re
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Dave Re
  • Re: Root remaining read-only after boot, no obvious reason why
    • From: Zbigniew Jędrzejewski-Szmek

• Prev by Date: Why does stopping mount units kill user sessions?
• Next by Date: Re: Why does stopping mount units kill user sessions?
• Previous by thread: Re: Root remaining read-only after boot, no obvious reason why
• Next by thread: Re: Root remaining read-only after boot, no obvious reason why
• Index(es):
  • Date
  • Thread