linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Remote NAS
Date: Wed, 23 Sep 2009 07:52:59 -0700 (PDT)	[thread overview]
Message-ID: <9510.91067.qm@web38801.mail.mud.yahoo.com> (raw)
In-Reply-To: <20090923075710.GA9409@cthulhu.home.robinhill.me.uk>


--- On Wed, 9/23/09, Robin Hill <robin@robinhill.me.uk> wrote:
> > Commercial flagging is writing like hell to the array,
> according to
> > iotop.  I don't know how else to assess what's
> going on.  The drives
> > are constantly hammering, and my Myth menu moves get
> very slow during
> > flagging, even with the latest 2TB disk drives and
> RAID10.
> > 
> Are you transcoding as well?  The flagging itself
> shouldn't write, but
> if you're transcoding as well (to cut the commercials) then
> it will have
> to write.  And slow menu moves would suggest
> database/CPU holdups -
> there should be no need to read from the recordings disk
> (actually, it
> may have to check the file exists, but that's it). 
> You didn't say
> whether your database is on the array or not (if you're
> booting from the
> array then I'd guess so though).

Not transcoding at the same time, just the standard commercial flagging.  The drive light is constantly on.  CPU is pretty busy (3GHz) reaching 180% when simultaneously flagging 2 videos.

The database in in the / partition of the array, and the videos are in the /home partition on it.  No idea why the array is so busy.


> If your aim is to improve performance then I'd recommend
> using a single
> (relatively small) drive for the main OS and database, and
> then one (or
> more) drives for the recordings.

My goal is to have two large drives in the HTPC and two out in the garage NASed, in RAID10 so that if my HTPC is stolen or there's a fire I'll still have my data.  But no one here seems to know how to specify the HTPC drives as one side of the mirror and the garage drives as the other.  

Needless to say I'd like performance to be good, but that's starting to look hopeless.



      

  parent reply	other threads:[~2009-09-23 14:52 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 [this message]
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
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=9510.91067.qm@web38801.mail.mud.yahoo.com \
    --to=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).