On 2013.12.30 at 23:17 +0100, Jan Kara wrote: > On Sun 29-12-13 15:24:06, Markus Trippelsdorf wrote: > > I came across the following strange issue today: > > > > markus@x4 tmp % rm -fr boost > > rm: cannot remove ‘boost/results/boost/bin.v2/libs’: Directory not empty > > markus@x4 tmp % ll boost/results/boost/bin.v2/libs > > total 68K > > drwxr-xr-x 17 markus markus 4.0K Dec 29 15:01 . > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:00 .. > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 move > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 mpl > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 msm > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 multi_array > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 multi_index > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:00 multiprecision > > drwxr-xr-x 6 markus markus 4.0K Dec 29 15:01 numeric > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 optional > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 parameter > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 phoenix > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 polygon > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 pool > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 python > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 serialization > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 test > > markus@x4 tmp % ll boost/results/boost/bin.v2/libs > > total 140K > > drwxr-xr-x 35 markus markus 4.0K Dec 29 15:01 . > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:00 .. > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 config > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 move > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 mpl > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 msm > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 multi_array > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 multi_index > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:00 multiprecision > > drwxr-xr-x 6 markus markus 4.0K Dec 29 15:01 numeric > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 optional > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 parameter > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 phoenix > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 polygon > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 pool > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 predef > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 preprocessor > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 program_options > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 property_map > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 property_tree > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 proto > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 ptr_container > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 python > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 random > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 range > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 ratio > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 rational > > drwxr-xr-x 5 markus markus 4.0K Dec 29 15:01 regex > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 scope_exit > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 serialization > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 signals > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 signals2 > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 smart_ptr > > drwxr-xr-x 4 markus markus 4.0K Dec 29 15:01 spirit > > drwxr-xr-x 3 markus markus 4.0K Dec 29 15:01 test > > markus@x4 tmp % rm -fr boost > > markus@x4 tmp % ll boost/results/boost/bin.v2/libs > > ls: cannot access boost/results/boost/bin.v2/libs: No such file or directory > > markus@x4 tmp % > Hum, my guess would be that some other process has been adding files to > the directory while the first 'rm -fr' was running. Thus rm got a list of > files in 'libs' to delete, deleted them, tried to delete 'libs' and failed > because the other process has added some new files / dirs in the mean time. > By the time you run second rm, the creating process has apparently > finished. I'm pretty sure that this wasn't the case. The boost test suite had finished and the machine was idle for a while, before I tried to remove the directory... -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
