No, the "zero dtime" is a thing that just essentially means that a
deleted inode was never actually written out to disk after being
deleted, and it's fairly normal.
>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).
But the above does sound very strange indeed. It's not necessarily the
disk, it could be memory or something else (the fact that it succeeds
the second time in fact implies that the image on the disk is fine, and
that the potential corruption happened somewhere else).
Linus
-
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