[systemd-devel] Antw: [EXT] Re: systemd autofs in RH 7

[Ulrich Windl]

>>> Silvio Knizek <killermoehre at gmx.net> schrieb am 21.04.2020 um 15:45 in
Nachricht
<24197_1587476741_5E9EF905_24197_143_1_61f65bea728c37e386b1212f4f282aefc193ab0c.
amel at gmx.net>:
> Am Dienstag, den 21.04.2020, 13:26 +0000 schrieb Wieschke, Thomas:
>> Hi,
>> I hope someone can help with the following case.
>>
>> I'm writing on a RH 7 system to an automounted FS and get an disruption 
> because systemd (??) is,
>> besides working in this directory, obviously trying an umount in the 
> background.
>> The umount doesn't work because the FS is in use (returned busy), but the 
> start/stop of autofs is
>> nevertheless done and leads to a disruption:
>>
>> Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on 
> demand...
>> ‑‑ Subject: Unit autofs.service has begun shutting down
>> ‑‑ Defined‑By: systemd
>> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel 
>> ‑‑
>> ‑‑ Unit autofs.service has begun shutting down.
>> Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: ask
umount 
> returned busy /vsaabrmount
>> Apr 21 12:02:20 server1 systemd[1]: Stopped Automounts filesystems on 
> demand.
>> ‑‑ Subject: Unit autofs.service has finished shutting down
>> ‑‑ Defined‑By: systemd
>> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel 
>> ‑‑
>> ‑‑ Unit autofs.service has finished shutting down.
>> Apr 21 12:02:20 server1 systemd[1]: Starting Automounts filesystems on 
> demand...
>> ‑‑ Subject: Unit autofs.service has begun start‑up
>> ‑‑ Defined‑By: systemd
>> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel 
>> ‑‑
>> ‑‑ Unit autofs.service has begun starting up.
>> Apr 21 12:02:20 server1 systemd[1]: Started Automounts filesystems on 
> demand.
>> ‑‑ Subject: Unit autofs.service has finished start‑up
>> ‑‑ Defined‑By: systemd
>> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel 
>> ‑‑
>> ‑‑ Unit autofs.service has finished starting up.
>> ‑‑
>> ‑‑ The start‑up result is done.
>>
>> Finally I tried to prevent any umount by changing in /etc/sysconfig/autofs

> #OPTIONS="" to OPTIONS="‑timeout=0"
>>
>> And I tried to add in /etc/auto.master at end of line ‑‑timeout=0 (/workdir
   
> /etc/auto.workdir ‑‑timeout=0)
>>
>> But besides this values there is an automatic restart every 30min
>>
>> Apr 21 13:34:41 server1 systemd: Stopping Automounts filesystems on 
> demand...
>> Apr 21 13:34:42 server1 systemd: Starting Automounts filesystems on 
> demand...
>> Apr 21 13:34:42 server1 systemd: Started Automounts filesystems on demand.
>> Apr 21 14:04:42 server1 systemd: Stopping Automounts filesystems on 
> demand...
>> Apr 21 14:04:42 server1 systemd: Stopped Automounts filesystems on demand.
>> Apr 21 14:04:42 server1 systemd: Starting Automounts filesystems on 
> demand...
>> Apr 21 14:04:42 server1 systemd: Started Automounts filesystems on demand.
>> Apr 21 14:34:42 server1 systemd: Stopping Automounts filesystems on 
> demand...
>> Apr 21 14:34:42 server1 automount[11019]: umount_autofs_indirect: ask
umount 
> returned busy /vsaabrmount
>> Apr 21 14:34:44 server1 systemd: Stopped Automounts filesystems on demand.
>> Apr 21 14:34:44 server1 systemd: Starting Automounts filesystems on 
> demand...
>> Apr 21 14:34:44 server1 systemd: Started Automounts filesystems on demand.
>>
>> Switching back to RH 6 doesn't show this problem.
>>
>> Any suggestions?
>>
>> Thanks in advance
>>
>> Best regards
>> Thomas
> 
> Hi Thomas,
> 
> don't use autofs, but systemd.automount for this. It does exactly what
> you want, but in the context of systemd. See man:systemd.automount for
> more information.

I wonder when we can boot systemd and run the kernel as an optional module
;-)
I guess the bootloader systemd.supergrub is almost complete meanwhile...

> 
> BR
> Silvio
> 
> _______________________________________________
> systemd‑devel mailing list
> systemd‑devel at lists.freedesktop.org 
> https://lists.freedesktop.org/mailman/listinfo/systemd‑devel