From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Remote NAS
Date: Tue, 22 Sep 2009 14:56:08 -0700 (PDT) [thread overview]
Message-ID: <151287.16979.qm@web38804.mail.mud.yahoo.com> (raw)
In-Reply-To: <20090922200912.GA28999@cthulhu.home.robinhill.me.uk>
Thanks Robin.
--- On Tue, 9/22/09, Robin Hill <robin@robinhill.me.uk> wrote:
> The BIOS boots from a single drive, and won't boot from
> RAID10, so
> presumably you already have a non-RAID (or RAID-1) boot
> partition.
I have my only two drives set up as RAID10offset2 (WD 2TB each), and it boots just fine for some reason.
> > > What if I use the mobo's e-SATA port to add 5
> external
> > > drives locally. This would require a port
> multiplier. I
> > > presume it would not be bootable, since a port
> multiplier
> > > needs OS support? Or would something go in
> initrd.img?
> > > Or would I need an individual boot drive to get
> things up?
> > >
> Depends on exactly how the BIOS sees is - some seem to see
> a single
> drive off the multiplier, so can boot off that one, whereas
> others won't
> see anything. The initrd question is immaterial, as
> this is only read
> after the BIOS has called the boot loader, but certainly
> you could load
> any necessary drivers at that point.
It's an Asus P5N7A-VM mobo, and of course Asus doesn't know the answer to this question. I have in mind the Addonics port "software" multiplier, which is a pure hardware multiplexer. (AD5SARPM-E with eSATA & Sii3726 chip)
I guess the answer is to just buy and try it. Reluctant to though, owing to the expense. I am surprised no one else has tried this.
> I'm not sure offset is really noticeably faster than far
> for writes.
> Commercial flagging shouldn't be writing to the recordings
> drive though
> - it's just inserting database metadata. If your
> MythTV database is on
> the same array/drives then you'll certainly get a big gain
> from moving
> it to a separate disk.
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.
next prev parent reply other threads:[~2009-09-22 21:56 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 [this message]
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
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=151287.16979.qm@web38804.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).