Package: fuseext2 Version: 0.4-1.1 Severity: normal Dear Maintainer,
* What led up to the situation? When using fuseext2 for mounting filesystem with block size > 4K, 1 CPU core is at 100% and directory with mount point is busy (when file image is mounted, then directory with this file is busy too). * What exactly did you do (or not do) that was effective (or ineffective)? i.e.: $ dd if=/dev/zero of=ext4-bs64k.img bs=1M seek=1M count=0 $ sudo /sbin/mkfs.ext4 -L TestExtFS -b 65536 ext4-bs64k.img $ fuseext2 ext4-bs64k.img /mount/somewhere/you/want * What was the outcome of this action? Filesystem is mounted without errors, but when any operation (i.e. ls -l) on mount point cause 100% of 1 CPU core and there is no expected output from operation. * What outcome did you expect instead? Working with mounted filesystem as usually (ls, cp, mv, mkdir, rm, rmdir, etc.) Sincerely Jarda -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fuseext2 depends on: ii e2fslibs 1.42.12-1 ii fuse 2.9.3-15+b1 ii libc6 2.19-13 ii libfuse2 2.9.3-15+b1 fuseext2 recommends no packages. fuseext2 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