From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: EXT2 data corruption 2.4.17-pre2
Date: Sat, 1 Dec 2001 03:12:43 -0700 [thread overview]
Message-ID: <20011201031243.B2412@vger.timpanogas.org> (raw)
Al Viro,
I am seeing subtle data corruption of inode data blocks on ext2
with 2.4.17-pre1/2. Large files being untarred over and over
and over again seem to trigger it, but it's hard to reproduce.
(i.e. I am building patches against several kernel trees).
I have gotten it to happen twice. In both cases, I get a CRC
error in a tar.gz and a message "skipping to next tar header"
furing this error. The data is totally corrupted in the tar.gz
when this problem shows up. It takes **HOURS** of heavy
untarring/diffing/untarring to make it show up.
Jeff
reply other threads:[~2001-12-01 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011201031243.B2412@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®