From: Hans Reiser <reiser@namesys.com>
To: edward@namesys.com
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: [reiserfs-list] Don't mix reiserfs and RAID5 in linux-2.4.1-pre8, severe corruption
Date: Sat, 20 Jan 2001 15:39:36 +0300 [thread overview]
Message-ID: <3A698708.A623EC44@namesys.com> (raw)
In-Reply-To: <3A68B126.7C5B6262@mail.infotel.ru>
Edward wrote:
>
> Reiserfs in linux-2.4.1-pre8 does not properly with the RAID5 code that
> is in that kernel. It is easy to get corrupted filesystem on device in
> less than 1 minute. Please, do not use it (reiserfs) on RAID5 devices.
> We are trying to figure out what is wrong.
>
> Edward
There is a report that it is not just reiserfs that has the corruption problem.
Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-20 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 21:27 Don't mix reiserfs and RAID5 in linux-2.4.1-pre8, severe corruption Edward
2001-01-19 18:59 ` [reiserfs-list] " Ed Tomlinson
2001-01-20 12:39 ` Hans Reiser [this message]
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=3A698708.A623EC44@namesys.com \
--to=reiser@namesys.com \
--cc=edward@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=reiserfs-list@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox