[Top] [All Lists]

Re: file corruption

To: linux-xfs@xxxxxxxxxxx
Subject: Re: file corruption
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Fri, 2 Apr 2004 00:33:54 -0900
In-reply-to: <20040402085020.GA28623@xxxxxxxxxxxxxxxxxxxxxxx>
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <406AF7B6.6030405@xxxxxxxxxxxxxxx> <20040402001801.GA24900@xxxxxxxxxxxxxxxxxxxxxxx> <406CB95B.4040500@xxxxxxxxxxxxxxx> <20040402043920.GF21226@xxxxxxxxxxxxxxx> <20040402044827.GC27240@xxxxxxxxxxxxxxxxxxxxxxx> <20040402071349.GH21226@xxxxxxxxxxxxxxx> <20040402085020.GA28623@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Fri, Apr 02, 2004 at 12:50:20AM -0800, Chris Wedgwood wrote:
> On Thu, Apr 01, 2004 at 10:13:49PM -0900, Ethan Benson wrote:
> > no more then 5 - 15 bytes or so.
> Sorry, I meant how large are the files ... not by how much are they
> shifted.
ah, various sizes

all the apache archived logs were affected (except the most recent
version as i recall).  they range from 500K to 5MB.

the rest of the compressed logs range form a couple K to aboug 800K.

> > 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).
> How can you tell if a compressed file is shifted 5-15 bytes?  Casual
> inspection will fail to decompress the data I would expect.

by hexdumping and comparing the corrupt versions with the good
versions on the original filesystem.

also the uncompressed logfiles exhibited the same corruption, which is
much more obvious to see.

> > however no other .gz file anywhere else in the filesystem was
> > corrupted in this manner.
> How recently had the logs been rotated before the unclean shutdown
> occurred?

2-4 weeks.  ive seen this on clean shutdowns after a filesystem copy
as well.

Ethan Benson

-- Attached file included as plaintext by Ecartis --

Version: GnuPG v1.2.4 (GNU/Linux)


<Prev in Thread] Current Thread [Next in Thread>