From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rearranging hard drives and data.
Date: Fri, 25 Dec 2020 03:41:26 -0600 [thread overview]
Message-ID: <0b0c2ea7-f3de-9201-bada-84790643f27a@gmail.com> (raw)
In-Reply-To: <X+CGSMpKYdKgExzU@tp>
Frank Steinmetzger wrote:
> Am Mon, Dec 21, 2020 at 03:19:08AM -0600 schrieb 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
>>
>> I was reading somewhere about FreeNAS OS that is commonly used on a NAS
>> and it uses ZFS. It sounded a lot like a LVM or BTRFS, (sp?), type file
>> system.
> ZFS combines LVM/RAID and the filesystem into one software. So you don't
> need to set up two separate layers (RAID and filesystem).
Hmmm. I'm not planing to use RAID so that could change things. I may
use some other OS/software. I'm not real quick to use Gentoo since it
likely won't be updated very often. I may research and see what else is
easy to install, will do what I want software wise and be OK with not
being updated very often. I read once where a guy built a file
server/NAS and stuck it in a closet. He used it all the time but just
never thought to go to the closet and do anything to it. I think he was
moving and was cleaning out the closet and realized how long it had been
sitting there untouched. He said it was dusty and had a uptime of over
5 years without a single update either. I may not be that bad but going
a year or so is certainly likely. Gentoo will not be happy with that.
Just have to wait and see I guess.
Dale
:-) :-)
next prev parent reply other threads:[~2020-12-25 9:41 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
2020-12-21 9:19 ` Dale
2020-12-21 11:26 ` Frank Steinmetzger
2020-12-25 9:41 ` Dale [this message]
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=0b0c2ea7-f3de-9201-bada-84790643f27a@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