Your message dated Mon, 6 Mar 2017 00:04:12 +0100
with message-id <24a671c2-5ba6-b9d9-dde5-b734ad11e...@debian.org>
and subject line Re: Bug#821944: [systemd] automounts not unmounted after
timeout
has caused the Debian Bug report #821944,
regarding [systemd] automounts not unmounted after timeout
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
821944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 229-4
Severity: normal
--- Please enter the report below this line. ---
I have an automount configured so that it should unmount after 300s, but it is
not unmounted:
From man systemd.automount:
TimeoutIdleSec=
Configures an idle timeout. Once the mount has been idle for the
specified time, systemd will attempt to unmount.
% cat /etc/systemd/system/mnt-vdr.automount
[Unit]
Description=VDR recordings
ConditionPathExists=/mnt/vdr
Wants=network.target
After=network.target
[Automount]
Where=/mnt/vdr
TimeoutIdleSec=300
[Install]
WantedBy=multi-user.target
% mount | grep vdr
systemd-1 on /mnt/vdr type autofs
(rw,relatime,fd=38,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
% cd /mnt/vdr markus@zem % mount | grep vdr
systemd-1 on /mnt/vdr type autofs
(rw,relatime,fd=38,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
vdr:/srv/share/vdr on /mnt/vdr type nfs
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.178.47,mountvers=3,mountport=48705,mountproto=tcp,local_lock=none,addr=192.168.178.47)
% cd ~
% sleep 400; mount | grep vdr
systemd-1 on /mnt/vdr type autofs
(rw,relatime,fd=38,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
vdr:/srv/share/vdr on /mnt/vdr type nfs
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.178.47,mountvers=3,mountport=48705,mountproto=tcp,local_lock=none,addr=192.168.178.47)
So after 400s it's still mounted. I guarantee that no other process
accessed /mnt/vdr in that time.
--- System information. ---
Architecture: amd64
Kernel: Linux 4.4.0-1-amd64
Debian Release: stretch/sid
700 testing www.deb-multimedia.org
700 testing security.debian.org
700 testing ftp2.de.debian.org
600 unstable ftp2.de.debian.org
500 utopic ppa.launchpad.net
500 saucy ppa.launchpad.net
500 grml-testing deb.grml.org
--- Package information. ---
Depends (Version) | Installed
=========================================-+-==================
libacl1 (>= 2.2.51-8) | 2.2.52-3
libaudit1 (>= 1:2.2.1) |
libblkid1 (>= 2.17.2) |
libcap2 (>= 1:2.10) |
libcryptsetup4 (>= 2:1.4.3) |
libdbus-1-3 (>= 1.1.1) |
libkmod2 (>= 5~) |
libpam0g (>= 0.99.7.1) |
libselinux1 (>= 2.1.9) |
libsystemd-journal0 (= 208-8) |
libudev1 (>= 189) |
libwrap0 (>= 7.6-4~) |
libsystemd-login0 (= 208-8) |
util-linux (>= 2.19.1-2) |
initscripts (>= 2.88dsf-53.2) |
sysv-rc |
udev |
acl |
adduser |
libcap2-bin |
Package Status (Version) | Installed
=============================-+-===========
udev | 229-4
Recommends (Version) | Installed
=============================-+-===========
libpam-systemd | 229-4
Suggests (Version) | Installed
=========================-+-===========
systemd-ui |
--- Output from package bug script ---
--
Markus Grunwald
https://www.the-grue.de
Fragen zur Mail? https://www.the-grue.de/mail_und_co
https://www.the-grue.de/~markus/markus_grunwald.gpg
--- End Message ---
--- Begin Message ---
Am 18.12.2016 um 23:23 schrieb Michael Biebl:
> Control: tags -1 + moreinfo unreproducible
>
> Hi,
>
> On Wed, 20 Apr 2016 18:49:21 +0200 Markus Grunwald <mar...@the-grue.de> wrote:
>> Package: systemd
>> Version: 229-4
>> Severity: normal
>>
>> --- Please enter the report below this line. ---
>>
>> I have an automount configured so that it should unmount after 300s, but it
>> is
>> not unmounted:
>>
>> From man systemd.automount:
>> TimeoutIdleSec=
>> Configures an idle timeout. Once the mount has been idle for the
>> specified time, systemd will attempt to unmount.
>>
>> % cat /etc/systemd/system/mnt-vdr.automount
>> [Unit]
>> Description=VDR recordings
>> ConditionPathExists=/mnt/vdr
>> Wants=network.target
>> After=network.target
>>
>> [Automount]
>> Where=/mnt/vdr
>> TimeoutIdleSec=300
>>
>> [Install]
>> WantedBy=multi-user.target
> ^
> remote-fs.target would probably be more suitable.
>
>
> Can you also attach the corresponding mount unit or fstab entry?
>
> Fwiw, I've tried (with systemd 232-7) both a local and remote
> (auto)mount.
>
> This is the /etc/fstab I used
>
> # local
> LABEL=test /mnt/local ext4
> noauto,x-systemd.automount,x-systemd.idle-timeout=30 0 0
> # remote
> 10.20.30.40 /mnt/remote nfs
> noauto,x-systemd.automount,x-systemd.idle-timeout=30 0 0
>
> In both cases, the idle timeout worked properly
> and the file systems were unmounted after 30 seconds.
Closing due to lack of further feedback and as I was not able to
reproduce the issue.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
