(I hope this is the right place for this question.)
I have managed to create a corrupt Directory on an ext3 partition. Corrupt in the sense that pathnames get too long, and I am unable to rmdir the offending directory; not corrupt in the sense that inodes are broken - at least not that I have seen evidence of. When I try to delete the directory using ROX-Filer I get
Code: Select all
...
ERROR: Directory not empty
ERROR: Directory not empty
ERROR: Directory not empty
Done
There were 382 errors.
which suggests to me this directory tree is somewhat more than 382 layers deep -- not counting the layers traversed before the first error.
What happened is that I somehow managed to launch a malformed mkdir -p script I was working on in Geany. I'm pretty certain I know when it happened, but not at all certain how I did it. That's not the point - I at least know to be more careful about what I'm doing with the mouse!
Long time windoze user- fairly accomplished DOS BAT scripter; just not well versed with Linux scripting and filesystems. I'm thinking that if I could force the release of the inode at the top of the corruption and then recover all the 'missing' inodes below that my problem would go away.
My problem is a) I don't know how to do that and b) is this even a valid, or reasonable, idea?
Advice appreciated!
Clif