Bug#881425: Info received (Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty))

2017-11-15 Thread Philipp Marek
Hmmm, using a VM I can't reproduce with 4.13.10-1... The "rm /*" is too fast, perhaps I need more background IO noise?

Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty)

2017-11-11 Thread Ben Hutchings
On Sat, 2017-11-11 at 16:53 +0100, Philipp Marek wrote: > Package: src:linux > Version: 4.13.4-2 > Severity: normal [...] Can you try the newer version in unstable? Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, reading IRC for the first time signature.asc Description: This

Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty)

2017-11-11 Thread Philipp Marek
I forgot to mention that I interrupted one of the earlier "rm /*" calls with Ctrl-C and, when that didn't react, I did Ctrl-Z a few times and then (on the shell) a "bg" - but that was too late, "rm" had already quit. But I interrupted only one "rm"; not later ones, and surely not the "rm -rf ");

Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty)

2017-11-11 Thread Philipp Marek
Package: src:linux Version: 4.13.4-2 Severity: normal My root FS is an /dev/mapper/n555--vg-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 Due to a programming error I filled one directory with many files; the "rm /*" I did previously couldn't copy anymore, so I ran "rm -rf ",