https://bugs.kde.org/show_bug.cgi?id=388360
Bug ID: 388360
Summary: SystemD auto-mount of (squashfs) filesystem causes
mount/unmount loop
Product: kfile
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kfileplacesview
Assignee: kdelibs-b...@kde.org
Reporter: marco.le...@gmx.de
CC: lu...@kde.org
Target Milestone: ---
I have an /usr/local/lib/systemd/system/usr-repos.automount containing the
following lines:
·✂··································
[Unit]
Description=Mounts the Portage tree
[Install]
WantedBy=local-fs.target
[Automount]
Where=/usr/repos
TimeoutIdleSec=10
·✂··································
accompanied by an /etc/fstab line:
/usr/repos.sfs /usr/repos squashfs noauto,noatime 0 0
Now whenever I browse to /usr using the "Details" view in Dolphin, /usr/repos
gets mounted to calculate and display the number of elements inside. The "Loop
Device" shows up in the places panel. So far so good. But when the 10 seconds
run out and the filesystem gets unmounted by SystemD, the places entry is left
behind. Then, immediately after the unmount, the filesystem gets mounted again
creating another "Loop Device" entry. This process repeats a few times creating
several dummy "Loop Device" displaying as unmounted. (Zombie "Loop Device"
entries have been reported as 369434 and 319998.)
- Restarting Dolphin cleans up the places panel.
- The steps above reproduce the issue for me, but the mount/unmount loop can be
triggered by other programs besides Dolphin AFAICT.
In the terminal output of krunner the mount/unmount can be followed as UDisks2
messages:
"/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces:
("org.freedesktop.UDisks2.Filesystem")
"/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces:
("org.freedesktop.UDisks2.Filesystem")
"/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces:
("org.freedesktop.UDisks2.Filesystem")
"/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces:
("org.freedesktop.UDisks2.Filesystem")
QFileInfo::absolutePath: Constructed with empty filename
Ideally, if some part of KDE still accesses the filesystem, the auto-unmount
timer should be reset and the loop device kept mounted, instead of triggering a
mount _right_ after the unmount.
--
You are receiving this mail because:
You are watching all bug changes.
