From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [somewhat OT] I just discovered that Stratis uses XFS.
Date: Tue, 2 Oct 2018 18:30:18 +0200 [thread overview]
Message-ID: <20181002183018.37343c26@harpe.intellique.com> (raw)
In-Reply-To: <6eb79c7b-4f15-28af-44b5-03488008a897@sandeen.net>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Le Tue, 2 Oct 2018 10:05:42 -0500
Eric Sandeen <sandeen@sandeen.net> écrivait:
> But if Stratis starts at 1TB it's not terrible; I'd need to look and
> see how many AGs get created (probably 4?) and if so, 250G AGs are
> not /too/ granular. If it's creating a lot more smaller AGs, that
> could become an issue if it gets grown to a very large size. IOWs
> the growfs concern is mostly about the resulting AG size & AG count.
>
You're right, I've looked through the source code and no option ever
gets passed to mkfs.xfs nor xfs_growfs related to FS size. That means
that it creates the FS with the default 4 AGs for a start.
--
------------------------------------------------------------------------
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 prev parent reply other threads:[~2018-10-02 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 14:25 [somewhat OT] I just discovered that Stratis uses XFS Emmanuel Florac
2018-10-02 14:37 ` Emmanuel Florac
2018-10-02 15:05 ` Eric Sandeen
2018-10-02 16:30 ` Emmanuel Florac [this message]
2018-10-03 22:47 ` Chris Murphy
2018-10-04 10:27 ` Emmanuel Florac
2018-10-02 21:46 ` 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=20181002183018.37343c26@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).