Whenever my LINUX 486 system (2.0.29) does an e2fsck (1.06), I get always
the same messages
"Deleted inode XYZ has zero dtime"
with the same inode numbers (automated e2fsck says it fixes the problem,
but it looks like it doesn't). Can someone tell me where's the problem, and
how to fix it?
I heard of anotherone who experienced the same problems.
Best wishes
Stephan
--
Stephan Fuhrmann, Stephan.Fuhrmann@stud.uni-karlsruhe.de
(Computer Science, University of Karlsruhe)