Package: jmtpfs Version: 0.5-2 Severity: normal How to reproduce:
0) mount your favourite android device with jmtpfs 1) note how much space you have in /tmp 2) rsync X (for X > 100) megabytes of files to your device 3) observe that /tmp now has a X less space, after rsync has terminated. 4) run something like "lsof | grep jmtpfs | grep deleted" to see that the jmtpfs process is hanging on to many deleted files in /tmp, at a guess from tmpfile 5) fusermount -u /your/mount/point to get your space back. This effectively means that sufficiently large trees cannot be rsynced, even in serveral tries, since /tmp fills up part way through. If you use cp -a instead of rsync, then /tmp usage seems roughly proportional to the largest file copied, and more importantly it is released after cp finishes. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages jmtpfs depends on: ii fuse 2.9.3-15+b1 ii libc6 2.19-13 ii libfuse2 2.9.3-15+b1 ii libgcc1 1:4.9.1-19 ii libmagic1 1:5.20-2 ii libmtp9 1.1.8-1+b1 ii libstdc++6 4.9.1-19 ii libusb-1.0-0 2:1.0.19-1 jmtpfs recommends no packages. jmtpfs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
