Debian Bug report logs - #1059270
e2fsprogs: e2scrub_reap.service triggers mount of nfs home before network is ready causing loop

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Rike-Benjamin Schuppner <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: e2fsprogs: e2scrub_reap.service triggers mount of nfs home before network is ready causing loop

Date: Fri, 22 Dec 2023 11:39:26 +0100

Package: e2fsprogs
Version: 1.47.0-2
Severity: important

Dear Maintainer,

we run a system with the /home folder living in a remote nfs server.
After upgrading to Debian 12, we noticed boot failures that were
apparently caused by the e2scrub_reap.service as this service triggers
an automount

    home.automount: Got automount request for /home, triggered by 924 ((crub_all))

which then, after a few minutes of waiting for timeouts, causes a few
other services to fail:

   mount.nfs4: Network is unreachable
   home.mount: Mount process exited, code=exited, status=32/n/a
   home.mount: Failed with result 'exit-code'.
   Failed to mount home.mount - /home.
   systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device
   systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: No such device
   NetworkManager.service: Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device
   NetworkManager.service: Failed at step NAMESPACE spawning /usr/sbin/NetworkManager: No such device
   Reached target remote-fs.target - Remote File Systems.
   chrony.service: Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device
   chrony.service: Failed at step NAMESPACE spawning /usr/sbin/chronyd: No such device

While the system appears to be usable, systemd shows the services as
having failed, and of course the few minutes of boot delay is also
something that we would like to avoid.


The fix that worked for us was to change the service setting in e2scrub_reap.service from
ProtectHome=read-only to

     [Service]
     ProtectHome=yes

which does not trigger the automount system.


-- System Information:
Debian Release: 12.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.utf-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages e2fsprogs depends on:
ii  libblkid1    2.38.1-5+b1
ii  libc6        2.36-9+deb12u3
ii  libcom-err2  1.47.0-2
ii  libext2fs2   1.47.0-2
ii  libss2       1.47.0-2
ii  libuuid1     2.38.1-5+b1
ii  logsave      1.47.0-2

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  <none>

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  <none>
pn  fuse2fs        <none>
pn  gpart          <none>
ii  parted         3.5-3

-- no debconf information

Send a report that this bug log contains spam.