| Whatever has caused the problems, does anyone have any ways of
sucessfully removing a duff directory?
I have a customer who's seeing the same kind of things -
a corrupt directory on a advfs file system which the usual
commands refuse to touch.
/prodsw/app106/wip/5.0.99/patch # ls
106
/prodsw/app106/wip/5.0.99/patch # ls -l
./106 not found
total 0
/prodsw/app106/wip/5.0.99/patch # file 106
file: Cannot get file status on 106.
106: cannot open for reading
vdump: unable to get info for file <./app106/wip/5.0.99/patch/106>;
[22] Invalid argument
It would seem given the ls differences it's actually
patch/. which is corrupt and hence patch/106 is inaccessible
when you try to do anything other than a simple ls it barfs.
We've tried rm -r and cp's and mv's and nothing seems to work.
He can restore an uncorrupted backup of the directory to elsewhere
but not to the original site of the directory.
I've suggested blowing it all away from a directory above and
restoring, and that if he's using v4.0+ then verify may clean it up,
otherwise I'm getting to be at a loss what to do.
There used to be some kind of binary/low level editing you could do
to hack up or break a file, I thought maybe if it was seen as not
being a corrupted directory but just a duff file then the rm might
stand a better chance, but from what I can tell this facility isn't
available on digital unix anyway.
Any bright suggestions welcomed...
Jo.
|