Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59382
| From | Philipp Marek <philipp@marek.priv.at> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf <directory>" fails with ENOTEMPTY (Directory not empty) |
| Date | 2017-11-11 17:20 +0100 |
| Message-ID | <uKGFH-47K-1@gated-at.bofh.it> (permalink) |
| References | <uKGml-3L1-3@gated-at.bofh.it> <uKGml-3L1-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
I forgot to mention that I interrupted one of the earlier "rm <dir>/*" 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 <dir>"); another "rm -rf <dir>" with 117963 files in there just worked normally right now. Seems that the interrupted unlinkat() call did something unusual?!
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf <directory>" fails with ENOTEMPTY (Directory not empty) Philipp Marek <philipp@marek.priv.at> - 2017-11-11 17:00 +0100 Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf <directory>" fails with ENOTEMPTY (Directory not empty) Philipp Marek <philipp@marek.priv.at> - 2017-11-11 17:20 +0100 Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf <directory>" fails with ENOTEMPTY (Directory not empty) Ben Hutchings <ben@decadent.org.uk> - 2017-11-11 20:50 +0100 Bug#881425: Info received (Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf <directory>" fails with ENOTEMPTY (Directory not empty)) Philipp Marek <philipp@marek.priv.at> - 2017-11-15 15:20 +0100
csiph-web