From: Hans Reiser <reiser@namesys.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Nikita Danilov <Nikita@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: Reiser4 problems
Date: Mon, 20 Oct 2003 16:29:36 +0400 [thread overview]
Message-ID: <3F93D530.4000105@namesys.com> (raw)
In-Reply-To: <3F93D4FD.8000801@cyberone.com.au>
Nick Piggin wrote:
>
>
> Hans Reiser wrote:
>
>> Nick Piggin wrote:
>>
>>>
>>>
>>> Nick Piggin wrote:
>>>
>>>>
>>>> filesystem created with default options, mounted with
>>>> noatime,nodiratime.
>>>> I'll try without the extra mount options now.
>>>>
>>>
>>> still no good
>>>
>>>
>>>
>>>
>> It is hardware error....
>
>
>
> Perhaps. However the same hardware can take heavy stressing with ext2,
> reports no errors with "badblocks", has never had any data corruption or
> any SCSI error reported unless using Reiser4, etc etc.
>
>
>
>
did you use the badblocks program?
--
Hans
next prev parent reply other threads:[~2003-10-20 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F928BE3.6070201@cyberone.com.au>
[not found] ` <3F929B2E.3020509@namesys.com>
2003-10-20 10:12 ` Reiser4 problems Nikita Danilov
2003-10-20 12:06 ` Nick Piggin
2003-10-20 12:09 ` Nick Piggin
2003-10-20 12:18 ` Hans Reiser
2003-10-20 12:28 ` Nick Piggin
2003-10-20 12:29 ` Hans Reiser [this message]
2003-10-20 12:34 ` Nick Piggin
2006-03-21 18:07 reiser4 problems Sergey Ivanov
2006-03-21 19:32 ` Hans Reiser
2006-03-21 21:20 ` Sergey Ivanov
2006-03-22 7:33 ` Vitaly Fertman
2006-03-22 13:21 ` sergey ivanov
2006-03-22 22:36 ` Jake Maciejewski
2006-03-23 6:46 ` Vladimir V. Saveliev
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=3F93D530.4000105@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=piggin@cyberone.com.au \
/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.