On Thu, Apr 01, 2004 at 08:48:27PM -0800, Chris Wedgwood wrote:
> On Thu, Apr 01, 2004 at 07:39:20PM -0900, Ethan Benson wrote:
>
> > I have seen this a few times as well, except the binary crap is
> > usually PREpended rather then appended to the file, also the end of
> > the file is usually cut off, as if the start and end markers were
> > equally offset backwards. (the start of the file moved back 5 or 10
> > bytes, and the end of the file moved back 5 or 10 bytes, thus causing
> > truncation and random crud being prepended).
>
> How much data are we talking about here? For > blocksize this seems
> impssible.
no more then 5 - 15 bytes or so.
its definitly quite strange, i couldn't really make any guess as to
what would cause it. but its definitly possible since ive seen it
happen several times on multiple files, each file affected in a
consistent way.
what i find most peculiar is how it consistently affected
/var/log/foo.gz.{1,2} but not {3,4} (or maybe it was {2,3} and {3,4} i
don't recall now).
however no other .gz file anywhere else in the filesystem was
corrupted in this manner.
--
Ethan Benson
http://www.alaska.net/~erbenson/
-- Attached file included as plaintext by Ecartis --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iEYEARECAAYFAkBtEq0ACgkQJKx7GixEevyeEQCfQBQiuEDe/recha0s8LOyUcYc
tIoAn1QAfeTiQTH071eKby4edCcsvtS7
=36sD
-----END PGP SIGNATURE-----
|