linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: NAS Remote Side of a Mirror
Date: Thu, 08 Oct 2009 14:10:11 +0100	[thread overview]
Message-ID: <4ACDE4B3.7000007@anonymous.org.uk> (raw)
In-Reply-To: <656255.26746.qm@web38802.mail.mud.yahoo.com>

On 08/10/2009 13:15, adfas asd wrote:
> --- On Thu, 10/8/09, John Robinson <john.robinson@anonymous.org.uk> wrote:
>> Hang on - you still need Samba to export a Linux filesystem
>> to Windows clients, don't you? And that's what a NAS has to
>> do.
> 
> Winduhs clients?  We don't need no steenkin' Winduhs clients...

In which case no, you don't need Samba, you never did need Samba and 
I've no idea why you were using it.

The QNAP NAS you linked to does export filesystems via SMB using Samba, 
as well as via AFS, NFS, FTP and HTTP. It can also export volumes via 
iSCSI. It almost certainly runs LVM over md RAID to do all these things.

If you want to build a box to put in your garage which exports raw discs 
over ethernet, you might want to consider nbd (Network Block Device) or 
similar, or iSCSI. If you want it to export files, you will need to run 
a filesystem and expose them using Samba, AFS or NFS, depending on your 
client and preference.

I have a box in my hall cupboard which has 3 1TB discs. They're 
partitioned into two partitions each. The first partitions make up md0 
with RAID-1 which mounts as /boot in the Xen dom0. The second partitions 
make up md1 with RAID-5 with a write-intent bitmap, over which I run 
LVM, which has logical volumes for the Xen dom0 root filesystem, various 
other Xen guests' filesystems, and a large filestore. The filestore 
volume is formatted ext3 and exported to the network with Samba to 
Windows clients and NFS to Linux clients. Fast clients also using 
gigabit ethernet manage ~80MB/s reading and ~60MB/s writing large files 
over either SMB or NFS. The machine also runs a MythTV backend. I have 
done some performance tuning to get where I am, some of it discussed on 
this list, and now I have no performance problems, and just look at all 
those layers...

Cheers,

John.

  reply	other threads:[~2009-10-08 13:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 15:37 NAS Remote Side of a Mirror adfas asd
2009-10-06 15:24 ` Robin Hill
2009-10-06 15:36   ` adfas asd
2009-10-07 23:49 ` adfas asd
2009-10-08  0:50   ` Chris Green
2009-10-08 11:39     ` adfas asd
2009-10-08 11:53       ` John Robinson
2009-10-08 12:15         ` adfas asd
2009-10-08 13:10           ` John Robinson [this message]
2009-10-08 13:39             ` adfas asd
2009-10-08  7:51   ` Robin Hill
2009-10-08 13:12     ` russ
2009-10-08 13:55       ` adfas asd
2009-10-10  7:13   ` Leslie Rhorer
2009-10-10 12:49     ` adfas asd
2009-10-10 14:21       ` Drew
2009-10-10 14:27         ` adfas asd
2009-10-10 14:28       ` Thomas Fjellstrom
2009-10-10 14:30         ` adfas asd
2009-10-11  7:00       ` Leslie Rhorer
  -- strict thread matches above, loose matches on Subject: below --
2009-10-08 13:06 adfas asd

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=4ACDE4B3.7000007@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --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).