From: "Ralf Groß" <ralf.gross+xfs@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: memory requirements for a 400TB fs with reflinks
Date: Sat, 20 Mar 2021 19:01:37 +0100 [thread overview]
Message-ID: <CANSSxym1ob76jW9i-1ZLfEe4KSHA5auOnZhtXykRQg0efAL+WA@mail.gmail.com> (raw)
Hi,
I plan to deploy a couple of Linux (RHEL 8.x) server as Veeam backup
repositories. Base for this might be high density server with 58 x
16TB disks, 2x RAID 60, each with its own raid controller and 28
disks. So each RAID 6 has 14 disks, + 2 globale spare.
I wonder what memory requirement such a server would have, is there
any special requirement regarding reflinks? I remember that xfs_repair
has been a problem in the past, but my experience with this is from 10
years ago. Currently I plan to use 192GB RAM, this would be perfect as
it utilizes 6 memory channels and 16GB DIMMs are not so expensive.
Thanks - Ralf
next reply other threads:[~2021-03-20 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 18:01 Ralf Groß [this message]
2021-03-22 16:50 ` memory requirements for a 400TB fs with reflinks Ralf Groß
2021-03-22 21:50 ` Dave Chinner
2021-03-23 9:39 ` Ralf Groß
2021-03-23 22:02 ` Dave Chinner
2021-03-23 9:31 ` Lucas Stach
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=CANSSxym1ob76jW9i-1ZLfEe4KSHA5auOnZhtXykRQg0efAL+WA@mail.gmail.com \
--to=ralf.gross+xfs@gmail.com \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.