From: Hans Reiser <reiser@namesys.com>
To: sander@humilis.net
Cc: ReiserFS List <reiserfs-list@namesys.com>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
dad <ramon.reiser@us.army.mil>
Subject: Re: My Dad suggests a redundant copies plugin
Date: Tue, 25 Oct 2005 02:28:05 -0700 [thread overview]
Message-ID: <435DFAA5.9050206@namesys.com> (raw)
In-Reply-To: <20051025072537.GB8402@favonius>
Sander wrote:
>Hans Reiser wrote (ao):
>
>
>>This would not be (at least in theory) useful for RAID devices, but for
>>a user with a single disk drive, it might be useful to have a plugin
>>that creates two (or N) copies, and tries to allocate the two copies at
>>opposite ends of the disk. Anyone out there still looking for a plugin
>>to write?
>>
>>
>
>That will kill performance badly. First of all the two read/writes
>needed, and second because you have to seek from one end to the disk to
>the other every time you read/write something.
>
>And what is the advantage? You are not protected against a lot of disk
>failures (only against bad blocks, right?).
>
>There is a lot more advantage in buying two disks and do raid over them.
>This is (much) cheaper, gives better performance and gives more
>protection.
>
>Anyway, no need for a plugin. You can just divide your disk in two
>partitions and configure them as a raid1.
>
>Or am I missing something in your suggestion?
>
>
>
It is only for very important files for computers which have only one
hard drive. Some of the work is with changing fsck.....
Hans
next prev parent reply other threads:[~2005-10-25 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 5:48 My Dad suggests a redundant copies plugin Hans Reiser
2005-10-25 7:25 ` Sander
2005-10-25 9:28 ` Hans Reiser [this message]
2005-10-25 9:39 ` Sander
2005-10-25 10:25 ` Konstantin Münning
2005-10-25 19:48 ` David Masover
2005-10-25 10:35 ` Ingo Bormuth
2005-10-26 16:24 ` Gregory Maxwell
2005-10-26 15:49 ` Charles P. Wright
[not found] ` <e692861c0510260917r36c2195fp367689753f61b307@mail.gmail.com>
2005-10-26 16:20 ` Fwd: " Gregory Maxwell
2005-10-26 18:22 ` Hans Reiser
2005-10-27 7:10 ` Sander
2005-10-27 11:24 ` David Masover
[not found] ` <e692861c0510260911h33c9e2f0x549223c60ddadaef@mail.gmail.com>
2005-10-26 16:19 ` Gregory Maxwell
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=435DFAA5.9050206@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=ramon.reiser@us.army.mil \
--cc=reiserfs-list@namesys.com \
--cc=sander@humilis.net \
/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.