Does a bunch of "Deleted inode x has zero dtime" at fsck time count as fs
corruption? I get these regularly when I force a fsck on an otherwise 'clean'
fs. It so happens that I have a Quantum Fireball in the box and now that
you've mentioned it I remembered the fsck complaints...
And now that I started thinking about it, I also remembered that tar sometimes
fails to unpack otherwise good gzipped tarballs (if I repeat the command,
everything is (usually) swell). I was blaming tar/gzip for this but now I'm not
so sure anymore (especially since I replaced both files and the problem still
persists).
2.0.35 UP (Cyrix P166), IDE here..
Andrej
-- Andrej Presern, andrejp@luz.fe.uni-lj.si- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html