From: "Lenar Lõhmus" <lenar@vision.ee>
To: Tomas Szepe <szepe@pinerecords.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes
Date: Sat, 29 May 2004 14:56:51 +0300 [thread overview]
Message-ID: <40B87A83.1020208@vision.ee> (raw)
In-Reply-To: <20040528162450.GE422@louise.pinerecords.com>
Tomas Szepe wrote:
>On May-28 2004, Fri, 08:46 -0400
>Chris Mason <mason@suse.com> wrote:
>
>
>
>>>The bottom line: I've experienced file corruption, of the following
>>>nature: consecutive regions (all, it seems, aligned on 256-byte
>>>boundaries, and typically around 1kb or 2kb in length) of seemingly
>>>random files are replaced by null bytes.
>>>
>>>
>>The good news is that we tracked this one down recently. 2.6.7-rc1
>>shouldn't do this anymore.
>>
>>
>
>So did this only affect SMP machines?
>
>
>
No, it's UP here. And I think it happened first with 2.6.6-rc2-mm2.
Lenar
next prev parent reply other threads:[~2004-05-29 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 12:28 filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes David Madore
2004-05-28 12:46 ` Chris Mason
2004-05-28 13:05 ` Lenar Lõhmus
2004-05-28 16:24 ` Tomas Szepe
2004-05-28 16:29 ` Chris Mason
2004-05-28 16:42 ` Pat
2004-05-28 16:54 ` Chris Mason
2004-05-28 16:45 ` Tomas Szepe
2004-05-28 16:55 ` Chris Mason
2004-05-28 16:58 ` Steven Cole
2004-05-29 11:56 ` Lenar Lõhmus [this message]
[not found] ` <1085750828.1914.385.camel@tribesman.namesys.com>
[not found] ` <1085751695.22636.3163.camel@watt.suse.com>
2004-05-31 16:48 ` I would like to see ReiserFS V3 enter a feature freeze real soon Hans Reiser
2004-06-01 11:37 ` Chris Mason
2004-06-01 17:02 ` Hans Reiser
2004-06-01 18:53 ` Chris Mason
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=40B87A83.1020208@vision.ee \
--to=lenar@vision.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.