| 1 |
On Mon, 7 Jun 2010 23:46:19 +0200, Alan McKinnon wrote: |
| 2 |
|
| 3 |
> Neil is likely correct - filesystem corruption. A quick easy way to |
| 4 |
> check is to run ls -al starting with the target then going up on |
| 5 |
> directory in turn. If you start getting lots of "???" in the output, |
| 6 |
> corruption is almost certain. |
| 7 |
|
| 8 |
Paul's suggestion of running lsof may be valid too. If a process had a |
| 9 |
lock n a file that was then deleted, the file wouldn't show up in ls but |
| 10 |
would prevent the directory being deleted until the lock was released. |
| 11 |
|
| 12 |
If you don't want to mess around with lsof and tracking down the process, |
| 13 |
a reboot will solve that one. |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Neil Bothwick |
| 18 |
|
| 19 |
If at first you don't succeed, call in an airstrike. |
Archives