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