On Monday 07 June 2010 22:24:37 Dale wrote: > Mick wrote: > > I am trying to clean up what seems like a remnant of a failed emerge, but > > I can delete the directory in question: > > > > # rm -Rf /var/tmp/portage/sys-devel/gcc-4.4.3- > > r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale > > rm: cannot remove `/var/tmp/portage/sys-devel/gcc-4.4.3- > > r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale': Directory > > not empty > > > > Am I missing something simple here? Why can't I remove it? It seems > > empty to me: > > > > # ls -la /var/tmp/portage/sys-devel/gcc-4.4.3- > > r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale > > total 1 > > drwxr-xr-x 2 portage portage 3 May 28 07:48 . > > drwxr-xr-x 3 portage portage 3 May 28 07:48 .. > > I generally use rm -rfv when I delete something and do it as root as > well. It is gone after that. I'm not sure what the difference is > between R and r tho. I need to go check the man page I guess. ;-)
The "#" in his quoted prompt implies that he is doing it as root. the -r -R and --recursive switches to rm are all synonymous. Neil is likely correct - filesystem corruption. A quick easy way to check is to run ls -al starting with the target then going up on directory in turn. If you start getting lots of "???" in the output, corruption is almost certain. -- alan dot mckinnon at gmail dot com
