From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: experience with very large filesystems
Date: Thu, 24 Feb 2022 08:10:06 +1100 [thread overview]
Message-ID: <20220223211006.GL59715@dread.disaster.area> (raw)
In-Reply-To: <20220223163513.43f1f054@harpe.intellique.com>
On Wed, Feb 23, 2022 at 04:35:13PM +0100, Emmanuel Florac wrote:
> 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?
From the filesystem side, that should not be an issue at all.
From the storage side, you really want to expand the storage with
chunks that have the same geometry (stripe unit and stripe width)
so that it doesn't screw up the alignment of the filesystem to the
new storage.
And that's where the difficultly may lie. If the existing storage
volume the filesystem sits on doesn't end exactly on a stripe width
boundary, you're going to have to offset the start of the new
storage volumes part way into the first stripe width in the volumes
to ensure that when the filesystem expands, then end of the first
stripe width in the new volume is exactly where the filesystem
expects it to be.
Other than that, there shouldn't be any filesystem level concerns
about doubling the size of the filesystem capacity via growfs.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-02-23 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 15:35 experience with very large filesystems Emmanuel Florac
2022-02-23 21:10 ` Dave Chinner [this message]
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=20220223211006.GL59715@dread.disaster.area \
--to=david@fromorbit.com \
--cc=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