From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NAS and replacing with larger drives
Date: Thu, 8 Dec 2022 17:30:18 -0600 [thread overview]
Message-ID: <015b49e3-a7d4-45f0-1ffd-b9be97215a54@gmail.com> (raw)
In-Reply-To: <CAGfcS_nX6ipPsRFj0SWoRpX23YdikcHzs2BRSukyPtCfuGD94Q@mail.gmail.com>
Rich Freeman wrote:
> On Thu, Dec 8, 2022 at 7:37 AM Dale <rdalek1967@gmail.com> wrote:
>> Path two, I've researched building a NAS using a Raspberry Pi 4 8GB as
>> another option. They come as parts, cases too, but the newer and faster
>> models of Raspberry Pi 4 with more ram seem to work pretty well.
> For this sort of application the key improvement of the Pi4 over its
> predecessors is IO. The Pi4 has USB3 and gigabit ethernet, and they
> are independent, so you get the full bandwidth of both (in theory).
> That is a massive step up over USB2 and 100Mbps ethernet that consumes
> the USB2 bandwidth.
>
> I can't really speak to the commercial solutions as I haven't used
> them. Main concern there is just the limited capacity, lack of
> expandability, and so on. Some are no doubt better than others in
> those regards.
>
> As far as DIY goes, you can definitely do all of that with a Pi4.
> Don't expect it to perform as well as sticking it on a decent amd64
> motherboard, but for backup and saturating the throughput of 1 hard
> drive at a time it can probably mostly make do. Encryption can be
> accomplished either with cryptsetup or a filesystem that has native
> encryption like ZFS. I've done both on Pi4s for storage. I will warn
> you that zfs encryption is not hardware-optimized on ARM, so that will
> not perform very well - it will be completely functional, but you will
> get CPU-bound. Linux-native encryption (ie cryptsetup/LUKS) will use
> hardware capabilities on the Pi4, assuming you're using something it
> supports (I think I'm using AES which performs adequately).
>
> For the Pi4 you would need to use USB storage, but for hard drives IMO
> this is perfectly acceptable, especially on a Pi. The gigabit
> ethernet and internal IO of the Pi is only going to max out one hard
> drive no matter how you connect it, so the USB3 interface will not be
> a bottleneck. On ARM SBCs that have PCIe you don't really get any
> better performance with an HBA and SATA/SCSI simply because the board
> IO is already pretty limited. USB3 is actually pretty fast for
> spinning disks, but depending on the number of hosts/etc it could
> become a bottleneck on a decent motherboard with a large number of
> drives. If you're talking about an amd64 with a 10GbE NIC and a
> decent HBA with sufficient PCIe lanes for both then obviously that is
> going to saturate more spinning disks. For NVMe you absolutely need
> to go that route (probably need to consider server-class hardware
> too).
>
> I use USB3 hard drives on Pis for my bulk storage because I care about
> capacity far more than performance, and with a distributed filesystem
> the performance is still good enough for what I'm doing. If I needed
> block storage for containers/VMs/whatever then use a different
> solution, but that gets expensive fast.
>
> Oh, one other thing. One of your issues is that you're using a backup
> solution that just dumps everything into a single file/directory and
> requires all the backup storage to be mounted at the same time in a
> single filesystem. There are solutions that do not have this
> requirement - particularly ones that are adaptable to tape.
> Unfortunately the best FOSS option I've found for this on linux is
> bacula and that is a serious PITA to use. If anybody has a better one
> I'm all ears (the requirement is to be able to store a backup across
> multiple hard drives, and this can't involve first storing it all in
> one place and then splitting it up later, or having more than one
> storage drive attached at the same time - basically I want to treat
> hard drives like tapes).
>
> If you're storing a LOT of backups then LTO is another option. Every
> time I do the math on that option it never makes sense unless you're
> backing up a LOT of data. If you got to a point where your backups
> consumed 10+ max-capacity hard drives it might start to make sense.
> Those USB3 hard drives on sale for $15/TB though are just really hard
> to beat when the tapes aren't all that much cheaper and the drives
> cost $1k.
>
From my understanding, you are right about USB3 and GB ethernet being
the big change. They also have more memory and faster CPUs but if you
bottleneck the data with slow USB and ethernet with the old ones, who
needs a fast CPU? I think they realized that the USB and ethernet had
to improve. It got better from there.
https://shop.allnetchina.cn/collections/sata-hat/products/dual-sata-hat-open-frame-for-raspberry-pi-4
I found the above. From my understanding, it allows a SATA drive to
connect to either 2 or 4 bays. That card appears to connect with USB3
ports but I can't see the bottom. Odds are, especially if data is
encrypted, the CPU will likely max out before the USB and ethernet. I'd
think anyway. From what little I've read, they seem to be pretty fast.
One thing I like about the Raspberry option, I can upgrade it later. I
can simply take out the old, put in new, upgrade done. If I buy a
prebuilt NAS, they pretty much are what they are if upgrading isn't a
option. Some of the more expensive ones may be upgradable, maybe.
I just wonder, could I use that board and just hook it to my USB port
and a external power supply and skip the Raspberry Pi part? I'd bet not
tho. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2022-12-08 23:30 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 12:37 [gentoo-user] NAS and replacing with larger drives Dale
2022-12-08 13:31 ` Mark Knecht
2022-12-08 13:58 ` Dale
2022-12-08 17:16 ` Mark Knecht
2022-12-08 23:35 ` Daniel Frey
2022-12-09 0:34 ` Dale
2022-12-10 0:10 ` Paul Colquhoun
2022-12-08 18:36 ` Wols Lists
2022-12-08 20:05 ` Mark Knecht
2022-12-08 20:44 ` Frank Steinmetzger
2022-12-09 13:13 ` Michael
2022-12-09 13:38 ` Frank Steinmetzger
2022-12-09 14:27 ` [OT] " Peter Humphrey
2022-12-09 14:38 ` Frank Steinmetzger
2022-12-10 0:41 ` Peter Humphrey
2022-12-09 15:28 ` Dale
2022-12-10 9:20 ` Wols Lists
2022-12-10 16:19 ` Frank Steinmetzger
2022-12-10 16:30 ` Wols Lists
2022-12-10 17:27 ` Michael
2022-12-10 18:17 ` David Rosenbaum
2022-12-11 4:45 ` David Rosenbaum
2022-12-09 14:15 ` Rich Freeman
2022-12-08 23:09 ` Dale
2022-12-08 13:52 ` Rich Freeman
2022-12-08 23:30 ` Dale [this message]
2022-12-08 23:38 ` Rich Freeman
2022-12-09 0:03 ` Dale
2022-12-09 0:17 ` Peter Humphrey
2022-12-09 0:45 ` Dale
2022-12-09 8:27 ` Wol
2022-12-09 10:34 ` Peter Humphrey
2022-12-11 11:34 ` [OT] " Peter Humphrey
2022-12-13 17:36 ` Laurence Perkins
2022-12-09 8:24 ` Wol
2022-12-09 0:06 ` Frank Steinmetzger
2022-12-09 1:15 ` Dale
2022-12-09 7:56 ` Wol
2022-12-09 9:15 ` Dale
2022-12-09 6:22 ` William Kenworthy
2022-12-08 13:59 ` Frank Steinmetzger
2022-12-08 14:11 ` Rich Freeman
2022-12-08 16:56 ` Laurence Perkins
2022-12-08 23:26 ` Rich Freeman
2022-12-09 14:11 ` Dale
2022-12-10 20:41 ` Dale
2022-12-10 21:28 ` Mark Knecht
2022-12-10 23:54 ` Dale
2022-12-11 3:31 ` Mark Knecht
2022-12-11 4:35 ` Dale
2022-12-11 14:07 ` Mark Knecht
2022-12-11 15:01 ` Dale
2022-12-11 15:44 ` Mark Knecht
2022-12-11 23:43 ` Frank Steinmetzger
2022-12-12 0:32 ` Dale
2022-12-12 1:55 ` Dale
2022-12-12 23:29 ` Mark Knecht
2022-12-13 0:43 ` Dale
2022-12-11 2:46 ` David Rosenbaum
[not found] ` <CAL+8heNN7CCQcTrhjuJboAnxvi7ACWVAgPuXqj3bwTPNaNQ94A@mail.gmail.com>
2022-12-11 2:49 ` David Rosenbaum
2022-12-11 4:38 ` David Rosenbaum
2022-12-16 4:08 ` Dale
2022-12-16 12:56 ` Frank Steinmetzger
2022-12-16 22:35 ` Dale
2022-12-16 19:12 ` Mark Knecht
2022-12-16 22:43 ` Dale
2022-12-16 23:49 ` Frank Steinmetzger
2022-12-17 3:50 ` Dale
2022-12-17 4:47 ` Frank Steinmetzger
2022-12-17 6:49 ` Dale
2022-12-17 13:54 ` Frank Steinmetzger
2022-12-17 15:15 ` Mark Knecht
2022-12-17 15:51 ` Dale
2022-12-17 16:09 ` Mark Knecht
2022-12-17 16:42 ` Dale
2022-12-17 17:18 ` Mark Knecht
2022-12-17 22:56 ` David Rosenbaum
2022-12-17 19:10 ` Wol
2022-12-17 20:03 ` Mark Knecht
2022-12-17 23:41 ` Dale
2022-12-18 14:04 ` Mark Knecht
2022-12-18 15:12 ` Dale
2022-12-18 15:27 ` Michael
2022-12-18 18:38 ` Dale
2022-12-18 18:55 ` Mark Knecht
2022-12-18 19:20 ` Dale
2022-12-18 19:25 ` Mark Knecht
2022-12-18 22:08 ` Dale
2022-12-19 21:13 ` ralfconn
2022-12-18 18:56 ` Frank Steinmetzger
2022-12-18 15:29 ` Frank Steinmetzger
2022-12-18 18:59 ` Dale
2022-12-18 19:53 ` Wol
2022-12-18 22:11 ` Dale
2022-12-19 11:08 ` Wols Lists
2022-12-20 6:52 ` Dale
2022-12-26 8:01 ` David Rosenbaum
2022-12-26 8:00 ` David Rosenbaum
2022-12-18 15:29 ` Mark Knecht
2022-12-18 15:38 ` Mark Knecht
2022-12-18 15:48 ` Living in NGL: was: " Jack
2022-12-18 16:17 ` Mark Knecht
2022-12-18 19:00 ` Jack
2022-12-18 19:07 ` Dale
2022-12-18 19:22 ` Mark Knecht
2022-12-18 19:30 ` Frank Steinmetzger
2022-12-18 20:06 ` Rich Freeman
2022-12-18 20:30 ` Mark Knecht
2022-12-18 20:34 ` Mark Knecht
2022-12-18 20:53 ` Frank Steinmetzger
2022-12-18 21:53 ` Dale
2022-12-18 22:08 ` Frank Steinmetzger
2022-12-18 22:18 ` Dale
2022-12-19 1:37 ` Rich Freeman
2022-12-19 5:11 ` Dale
2022-12-19 12:00 ` Rich Freeman
2022-12-19 12:51 ` Wols Lists
2022-12-19 13:30 ` Rich Freeman
2022-12-19 16:43 ` Mark Knecht
2022-12-20 0:00 ` Rich Freeman
2022-12-20 1:46 ` William Kenworthy
2022-12-18 17:11 ` Wol
2022-12-18 18:03 ` Mark Knecht
2022-12-18 0:20 ` Wol
2022-12-17 20:47 ` Frank Steinmetzger
2022-12-21 0:14 ` Frank Steinmetzger
2022-12-21 2:47 ` Dale
2022-12-21 5:53 ` Wols Lists
2022-12-21 6:19 ` Frank Steinmetzger
2022-12-21 7:01 ` William Kenworthy
2022-12-21 20:03 ` Wol
2022-12-21 20:40 ` Frank Steinmetzger
2022-12-21 21:33 ` Wol
2022-12-21 6:52 ` Dale
2022-12-21 13:50 ` Mark Knecht
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=015b49e3-a7d4-45f0-1ffd-b9be97215a54@gmail.com \
--to=rdalek1967@gmail.com \
--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