From: Oleg Drokin <green@namesys.com>
To: Russell Coker <russell@coker.com.au>
Cc: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: ReiserFS is not suitable for a root FS.
Date: Sat, 17 May 2003 15:40:07 +0400 [thread overview]
Message-ID: <20030517114007.GA20790@namesys.com> (raw)
In-Reply-To: <200305172132.34865.russell@coker.com.au>
Hello!
On Sat, May 17, 2003 at 09:32:34PM +1000, Russell Coker wrote:
> > > Having the kernel just trash system memory because of bad data on disk is
> > > a bug.
> > You cannot check all the on disk values, this is too bik performance
> > impact. Nobody does that in Linux, I think.
> I really doubt that.
> On 99.99% of all machines in use the data can be checked much faster than it
> can be read from disk. There is little benefit in not checking, but there
> are huge problems when something goes wrong if you don't check.
> Corrupted disks are not uncommon. Otherwise we wouldn't need fsck programs!
Turn on CONFIG_REISERFS_CHECK and notice how you became CPU-bound instead of disk bound
suddenly.
Nobody does this in general case in linux.
Bye,
Oleg
next prev parent reply other threads:[~2003-05-17 11:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 10:30 ReiserFS is not suitable for a root FS Russell Coker
2003-05-17 10:56 ` Oleg Drokin
2003-05-17 11:09 ` Russell Coker
2003-05-17 11:24 ` Oleg Drokin
2003-05-17 11:32 ` Russell Coker
2003-05-17 11:40 ` Oleg Drokin [this message]
2003-05-17 11:14 ` Carl-Daniel Hailfinger
2003-05-17 11:25 ` Russell Coker
2003-05-17 12:01 ` Carl-Daniel Hailfinger
2003-05-17 12:10 ` Oleg Drokin
2003-05-19 10:22 ` Carl-Daniel Hailfinger
2003-05-19 10:31 ` Oleg Drokin
2003-05-21 22:09 ` Newsmail
2003-09-18 11:50 ` Carl-Daniel Hailfinger
2003-09-18 14:05 ` Vitaly Fertman
2003-05-17 12:40 ` Russell Coker
2003-05-19 19:55 ` bscott
2003-05-19 20:42 ` Dieter Nützel
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=20030517114007.GA20790@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.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.