From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: 2.4.5 corruption (again)
Date: Tue, 19 Jun 2001 06:52:33 -0700 [thread overview]
Message-ID: <200106191352.f5JDqXO12351@work.bitmover.com> (raw)
OK, my corruption is back and this time I'm saving the data. Al, send some
email when you are around, we can talk about access to the data. I'm tarring
up both good & bad right now. I've looked at a few files and they look
"shifted".
extra junk
original file less sizeof(extra junk) bytes
The machine has been up 6 days since the last corruption happened and the
process which detected the corruption ran successfully every night as well
as about 4 times by hand after my last corroption report.
next reply other threads:[~2001-06-19 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 13:52 Larry McVoy [this message]
2001-06-19 19:20 ` 2.4.5 corruption (again) Alexander Viro
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=200106191352.f5JDqXO12351@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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