linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Remote NAS
Date: Mon, 28 Sep 2009 08:15:47 -0600	[thread overview]
Message-ID: <200909280815.47537.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <41943.20139.qm@web38801.mail.mud.yahoo.com>

On Mon September 28 2009, adfas asd wrote:
> I am puzzled by why write-mostly.  Ostensibly Gb ethernet is supposed to
>  nearly equal the data transfer rate of the controller cards, and be many
>  times the speed of actual data transfer from the drives.
> 
> So shouldn't a NAS have plenty of bandwidth to accommodate most any drive
>  operations?

My GbE lan gets about 90MiB/s, my pcie sata card has shown upwards of 
400MiB/s. I haven't done full tests on the sata card yet, but it clearly is 
able to more than saturate a single GbE connection.

> I will be setting up a small high-perf drive for / (including database) so
>  the only data on the array will be /home (including large videos).
> 
> Seems like there is no need to specify write-mostly?
> 
> --- On Sun, 9/27/09, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
> >     In his situation (assuming he doesn't
> > take my advice and separate
> > the remote system entirely), wouldn't he be better served
> > to create a RAIDn
> > array on both systems and then create a RAID1 from the
> > local and NAS array
> > with the write mostly option?
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Thomas Fjellstrom
tfjellstrom@shaw.ca

  reply	other threads:[~2009-09-28 14:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 19:38 Remote NAS adfas asd
2009-09-22 20:09 ` Robin Hill
2009-09-22 21:56   ` adfas asd
2009-09-23  7:57     ` Robin Hill
2009-09-23  9:13       ` Keld Jørn Simonsen
2009-09-23 14:59         ` adfas asd
2009-09-23 21:01           ` Keld Jørn Simonsen
2009-09-23 22:58             ` adfas asd
2009-09-23 14:52       ` adfas asd
2009-09-23 15:29         ` Robin Hill
2009-09-23 15:44           ` adfas asd
2009-09-23 16:10             ` Robin Hill
2009-09-27 20:19               ` Leslie Rhorer
2009-09-28 14:07                 ` adfas asd
2009-09-28 14:15                   ` Thomas Fjellstrom [this message]
2009-09-29 14:40                     ` adfas asd
2009-09-29  9:25                   ` Leslie Rhorer
2009-09-27 20:44           ` Leslie Rhorer
2009-09-27 22:00         ` Leslie Rhorer
2009-09-29 14:15           ` adfas asd
2009-09-30 15:36             ` Leslie Rhorer
     [not found] <228497.14504.qm@web38801.mail.mud.yahoo.com>
2009-09-29 10:09 ` Leslie Rhorer
     [not found] <20090923200257.GA19027@cthulhu.home.robinhill.me.uk>
2009-09-23 23:08 ` adfas asd
  -- strict thread matches above, loose matches on Subject: below --
2009-09-16 16:21 adfas asd
2009-09-27 19:39 ` Leslie Rhorer
2009-09-27 20:09 ` Leslie Rhorer

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=200909280815.47537.tfjellstrom@shaw.ca \
    --to=tfjellstrom@shaw.ca \
    --cc=chimera_god@yahoo.com \
    --cc=linux-raid@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).