ext3-fs error (bad entry in directory)

Markus Oehme veelai at jonglieren-jena.de
Wed Dec 23 16:23:53 UTC 2009


At Tue, 22 Dec 2009 11:15:03 -0600,
Eric Sandeen wrote:
> > The message is always exactly the same. Somebody have a clue as to what is
> > going on here? And an easier question: How do I find out which directory is
> > #17083?
> 
> you can use debugfs:
> 
> debugfs:  ncheck
> ncheck: Usage: ncheck <inode number> ...
> debugfs:  ncheck 6031
> Inode	Pathname
> 6031	//testfilename

That solved the problem. We must have had a failed write there, I found an
empty directory, that should have been a file by the semantics, quite
strange. Fortunately I could simply delete it and now everything seems to be
fine.

Thanks a lot for the pointer.

       	 Markus

--
My key: http://users.minet.uni-jena.de/~veelai/veelai.gpg
--
For instance, on the planet Earth, man had always assumed that he was more
intelligent than dolphins because he had achieved so much---the wheel, New
York, wars and so on---while all the dolphins had ever done was muck about
in the water having a good time. But conversely, the dolphins had always
believed that they were far more intelligent than man---for precisely the
same reasons. (Douglas Adams, The Hitchhikers Guide to the Galaxy.)




More information about the Ext3-users mailing list