From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rearranging hard drives and data.
Date: Mon, 21 Dec 2020 10:52:50 +0800 [thread overview]
Message-ID: <99f61f01-e86f-a3b5-6349-f146cba40a3b@iinet.net.au> (raw)
In-Reply-To: <8074cb40-2345-4a25-0e17-8034c0159c5c@gmail.com>
On 21/12/20 8:20 am, Dale wrote:
> Howdy,
>
> Somewhat related. I googled and it appears I can hook a NAS to my
> router and share it there. The router is 1GB, it has yellow ports. Is
> it true that I can hook a NAS to the router? I'd assume it can be
> shared with anything connected to the router, even my cell phone if
> needed.
>
> Also, I'm looking at a new network card for my PC. With the new much
> faster internet coming soon, I need a faster network card. Router is
> ready, puter isn't. I found this, sorry for the caps but copy and
> paste. INTEL GIGABIT DUAL PORT NETWORK ADAPTER PCIe 424RR i350 1GB. I
> found a site that talks about NAS and network cards. According to the
> article, this should be a very reliable card and just works. It has two
> ports. I know I need one to hook to the router. Would that second port
> cause me any grief? Result in conflicts or something? I been using
> Realtek but article claims these are better. Anyone have thoughts on
> this? Have one and can share their experience?
>
> Thanks.
>
> Dale
>
> :-) :-)
>
Something to look into before going the traditional raid/nfs route:
moosefs or lizardfs. I am using arm based odroid HC2's and over the
softraid based nfs I was using there are considerable power savings
(especially if you take into the account redundancy) as it takes a
number of these low power arm systems to match the power requirements of
an older desktop), better data protection (actual, not theoretical for
2x raid 4 disk 10's replaced by a single 5x hc2's using the same disks
with mfs :) and the ease of mounting it into the filesystem. Downside
is needing a fast network for best performance but an NFS will need that
anyway for similar reasons.
BillK
next prev parent reply other threads:[~2020-12-21 2:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 13:02 [gentoo-user] Rearranging hard drives and data Dale
2020-12-19 13:47 ` bobwxc
2020-12-19 16:51 ` David Haller
2020-12-19 17:28 ` Dale
2020-12-19 18:37 ` antlists
2020-12-19 18:49 ` David Haller
2020-12-19 20:10 ` antlists
2020-12-19 21:31 ` David Haller
2020-12-19 23:21 ` Wols Lists
2020-12-19 17:06 ` Neil Bothwick
2020-12-19 17:32 ` Dale
2020-12-19 17:48 ` Neil Bothwick
2020-12-19 17:54 ` Dale
2020-12-19 21:48 ` Neil Bothwick
2020-12-20 1:02 ` Dale
2020-12-19 18:55 ` antlists
2020-12-19 19:19 ` Dale
2020-12-20 1:06 ` Frank Steinmetzger
2020-12-20 3:01 ` Dale
2020-12-20 14:21 ` Frank Steinmetzger
2020-12-20 22:37 ` Dale
2020-12-20 10:03 ` antlists
2020-12-20 13:20 ` Frank Steinmetzger
2020-12-20 13:39 ` Mark Knecht
2020-12-21 0:33 ` antlists
2020-12-21 0:20 ` Dale
2020-12-21 2:52 ` William Kenworthy [this message]
2020-12-21 9:19 ` Dale
2020-12-21 11:26 ` Frank Steinmetzger
2020-12-25 9:41 ` Dale
2020-12-21 10:48 ` Frank Steinmetzger
2020-12-21 12:53 ` Dale
2020-12-22 0:12 ` antlists
2020-12-24 16:38 ` Dale
2020-12-24 20:33 ` Frank Steinmetzger
2020-12-25 9:15 ` Dale
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=99f61f01-e86f-a3b5-6349-f146cba40a3b@iinet.net.au \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.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