Date: Fri, 23 Nov 2018 14:02:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233436] rm -rf fails when the number of subfolders of a folder in a tree is too high Message-ID: <bug-233436-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233436 Bug ID: 233436 Summary: rm -rf fails when the number of subfolders of a folder in a tree is too high Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: liedtke@punkt.de Hi, I stumbled over something, which I think should not happen: A customer asked me to delete some releases of theirs, which their deployme= nt tool did not clean up properly.=20 so I tried to rm -rf <Release>, which gave me the following result. rm -rf <release> rm: <release>/foo/bar/5a4b9dcdc0385d3e9d0827907f0e5f10792a8e7f: Operation n= ot permitted rm: <release>/foo/bar/f98dba83270209e862dbe2295bd078702bb9fa21: Operation n= ot permitted rm: <release>/foo/bar/48c4b74bceb996f66faec0e21aa97fb8d0607516: Operation n= ot permitted rm: <release>/foo/bar/415a52f0bd4ccbea7aadc1a15193b06da3366c37: Operation n= ot permitted rm: <release>/foo/bar/e475e6ed6fa28e141979cae142ef3a2faf6d9726: Operation n= ot permitted rm: <release>/foo/bar/dd7c1138264e4e8f3cebcbc16b00fac10fa629b5: Operation n= ot permitted rm: <release>/foo/bar/76789f907156f96e34f442785dfa7915c8c785ed: Operation n= ot permitted rm: <release>/foo/bar/7ecf83bcb737a84d8de66e7365b91ce27f778ea4: Operation n= ot permitted rm: <release>/foo/bar/b601d1dd9812e1b57e50d46edd2a891969b353f3: Operation n= ot permitted rm: <release>/foo/bar/0dd0c3382236ba9f2d6b3828dc305c2a01f45e87: Operation n= ot permitted rm: <release>/foo/bar: Directory not empty rm: <release>/foo: Directory not empty rm: <release>: Directory not empty So I went into <release>/foo/bar and did an ls, which showed me a big numbe= r of subdirectories like this: ls -la <Release>/foo/bar drwxrwxrwx 2 proserver proserver 3 Jun 7 10:44 ffc6821a8591392ebe03779270c8ec6e843a2b96 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:44 ffc927f8cc14ce68abdefcbea8f01542c892aea6 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:42 ffcaabb22cd01c67eb90dc8ee90f488427e987c3 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:43 ffcafbcd303e3ed81789be0930ba3b8999827443 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:42 ffcc53a0a31a38f18065861c42d0de0636140067 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:44 ffccb4ae42018024a90d0cdb7e635f714daef3d6 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:44 ffcd2c48e4171f25b96587da22a262f11c3123b8 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:43 ffcd73a168063217dab0ebf35a9ba16b5843c9f1 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:44 ffd0a1faba88fef9e2dec753ecfcbf2391f44f66 drwxrwxrwx 2 proserver proserver 3 Jun 7 10:43 ffd28f6ecac48500499e4803aef1a0b1f904129b counting the number of subdirectories gave me this: ls -la | wc -l 51550 in other release-directories this could be even 80000+ trying to delete them in <release>/foo/bar: rm -rf * su: /bin/rm: Argument list too long which was expected, but not with rm -rf I was able to delete them with find in the end but I thought rm -rf would do the trick. Am I wrong here or is it a bug? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233436-227>