From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: jose@tridentemonigotes.com, reiser <reiserfs-list@namesys.com>
Subject: Re: Desaster Reiser
Date: Thu, 05 Sep 2002 15:04:21 +0400 [thread overview]
Message-ID: <3D773A35.5070702@namesys.com> (raw)
In-Reply-To: 20020905140942.B19752@namesys.com
Oleg Drokin wrote:
>Hello!
>
>On Thu, Sep 05, 2002 at 10:53:35AM -0400, jose@tridentemonigotes.com wrote:
>
>
>> -I have a server 2.4.3 and something HD reiserfs. Yesterday one
>>of this
>>HD started to give me problems this is the message.
>>
>>
>
>2.4.3 kernel is very old ad is filled with known bugs both in reiserfs and other
>parts of code. You should consider upgrading.
>
>
>
>>
>>
Let's put this a bit more strongly. 2.4.3 should never have shipped to
users. It particularly has a ridiculously easy to hit bug in VFS that
affected reiserfs that would have been found if there was a policy of
test before shipping VFS changes. No one should be using it, and it is
definitely worth your time to upgrade.
We also have some not so easy but still possible to hit bugs in reiserfs
up until 2.4.18. I suggest 2.4.19/18 which is known to be rock stable
for us.
2.4.20-pre2 has some substantial performance improvements, but is more
risky as it has not been as well tested.
Hans
next prev parent reply other threads:[~2002-09-05 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 14:53 Desaster Reiser jose
2002-09-05 10:09 ` Oleg Drokin
2002-09-05 11:04 ` Hans Reiser [this message]
2002-09-05 16:32 ` Rafael E. Herrera
2002-09-05 20:02 ` Hans Reiser
[not found] ` <3D78CC6C.C09012AE@tridentemonigotes.com>
2002-09-06 16:06 ` jose
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=3D773A35.5070702@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=jose@tridentemonigotes.com \
--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 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.