From: Emmanuel Florac <eflorac@intellique.com>
To: linux-xfs@vger.kernel.org
Subject: experience with very large filesystems
Date: Wed, 23 Feb 2022 16:35:13 +0100 [thread overview]
Message-ID: <20220223163513.43f1f054@harpe.intellique.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi everyone,
I have a large filesystem (1.2 PiB) that's been working flawlessly for
4 years (an LV aggregating 4 300~ish TB RAID-6 arrays). However it's
getting really full (more than 1.1 PiB full right now), and I'm
considering expanding it to 1.8 PiB or more.
Any thoughts, caveats or else?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next reply other threads:[~2022-02-23 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 15:35 Emmanuel Florac [this message]
2022-02-23 21:10 ` experience with very large filesystems Dave Chinner
2022-02-24 12:09 ` Emmanuel Florac
2022-02-24 20:58 ` Dave Chinner
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=20220223163513.43f1f054@harpe.intellique.com \
--to=eflorac@intellique.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox