On Sun, 29.03.15 17:12, Kai Krakow (hurikha...@gmail.com) wrote: > Hello! > > I've got a automount point for a daily USB backup job. Due to some > instabilities of early USB3 chipsets and early USB3 devices, the mounted > device sometimes wents offline and eventually comes back after a while but > my backup job is stuck (rsync). I configured rsync to shutdown upon block io > timeouts. This in turn makes the systemd automounter think (correctly) that > the mount point is no longer in use - but it cannot be unmounted. The > problem here is, that it spams the journal with hundreds of messages per > minute all day long (or as long as I don't reboot):
Hmm? The systemd automount logic so far does not support mount expiration, hence I cannot really parse what you write above? > Mär 29 16:49:00 jupiter umount[19547]: umount: /mnt/private/usb-backup: > umount fehlgeschlagen: Die Operation ist nicht erlaubt Why does this fail with EPERM? I don't really follow I must admit... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
