From: Keith Lea <keith@cs.oswego.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test11 data loss
Date: Wed, 24 Dec 2003 16:59:24 -0500 [thread overview]
Message-ID: <3FEA0C3C.9090601@cs.oswego.edu> (raw)
Hello, I'm not subscribed to this list. This is not a help request, and
not really a bug report, I just thought someone should know about this.
I installed the 2.6.0-beta11-mm kernel last week, and the other day my
computer locked up (this is normal on my laptop with every kernel
version I've tried, this isn't the problem I'm posting about). When I
restarted, many, many files that had been open when it locked up were
filled with garbage, or the contents of totally unrelated files. For
example, my syslog contained some KDE header file code, and
/sbin/modprobe contained 82kb of data that seemed like random noise. I
think each file was the same size as it was originally, just with
different data, but I'm not sure.
The corruption happened on two separate partitions on a single IDE
laptop drive, and both were ReiserFS 3.6 partitions. I don't know if
this is a kernel bug or a Reiser bug or something else, but I thought
the kernel developers should know about this, and be on the lookout for
similar things (hopefully with more informative bug reports than mine).
I'm sorry I don't have more information, but if anyone wants to know
more about my system I'd be glad to help.
-Keith Lea
next reply other threads:[~2003-12-24 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 21:59 Keith Lea [this message]
2003-12-24 22:22 ` 2.6.0-test11 data loss Gergely Tamas
2003-12-24 22:34 ` Con Kolivas
2003-12-25 2:07 ` Eric D. Mudama
2003-12-25 5:17 ` Con Kolivas
2003-12-25 6:15 ` Hans Reiser
2003-12-25 16:46 ` Tomas Szepe
2003-12-25 23:45 ` Hmamouche, Youssef
2003-12-25 1:21 ` Felipe Alfaro Solana
2003-12-25 6:11 ` Hans Reiser
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=3FEA0C3C.9090601@cs.oswego.edu \
--to=keith@cs.oswego.edu \
--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