From: Wols Lists <antlists@youngman.org.uk>
To: Alex <mysqlstudent@gmail.com>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommendations for RAID setup needed
Date: Tue, 15 Sep 2015 19:08:31 +0100 [thread overview]
Message-ID: <55F85E9F.1070100@youngman.org.uk> (raw)
In-Reply-To: <CAB1R3sjKb-aXJV+4E5t6OsWid4QB+r6aCteZt+F+57=cWLhHWw@mail.gmail.com>
On 15/09/15 18:39, Alex wrote:
> Hi,
> I have a fedora22 system and would like to build a backup server. I
> have four 3TB SATA disks and would like to build a RAID5 array. I
> understand rebuild times can be extensive, possibility creating a
> scenario where another disk fails during that rebuild time, but I'm
> not sure I want to lose the extra space with creating a RAID6 array. I
> believe RAID5 also has faster write speeds?
What disks are you using? Are they proper raid disks? A 12TB array can
have a soft read error every complete pass, and still be within the
disk-manufacturer's specs. If your disks are not raid-compliant, this
will stop your array from rebuilding, ever!
(Chances are, your disks are above spec and won't give a problem. Do you
want to take the risk?)
>
> Is a 9TB RAID5 partition too risky in terms of rebuild time?
>
> What's the preferred filesystem for a backup server these days? Should
> I use XFS or ext4?
Throwing something completely different into the mix, how about
considering btrfs? It's not 100% solid yet, so you need to be careful
with it, but if you back up with rsync and the "in place" option, it'll
give you full backups for the cost of incremental.
What you MUST do is KEEP AN EYE ON DISK SPACE! The main failure mode for
btrfs I'm aware of, is that a disk full can cause a fatal error. As in
"I've just trashed the disk - it's 'format c:' time". So if you hit 80%
or so, alarm bells should be ringing. Very loud.
>
> Thanks,
> Alex
Cheers,
Wol
next prev parent reply other threads:[~2015-09-15 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 17:39 Recommendations for RAID setup needed Alex
2015-09-15 18:08 ` Wols Lists [this message]
2015-09-15 18:44 ` Alex
2015-09-16 2:12 ` Adam Goryachev
2015-09-16 10:03 ` Jens-U. Mozdzen
2015-09-16 15:53 ` Alex
2015-09-18 11:25 ` Michael Tokarev
2015-09-18 12:55 ` Alex
2015-09-15 18:57 ` Roman Mamedov
2015-09-22 4:18 ` David C. Rankin
2015-09-22 4:16 ` David C. Rankin
2015-09-22 5:03 ` Roman Mamedov
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=55F85E9F.1070100@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mysqlstudent@gmail.com \
/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).