All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [somewhat OT] I just discovered that Stratis uses XFS.
Date: Wed, 3 Oct 2018 16:47:05 -0600	[thread overview]
Message-ID: <CAJCQCtQyXjB1bzOWuj8f+cd-WgFkxDY8xpZ8YhVoTC72rPLThA@mail.gmail.com> (raw)
In-Reply-To: <20181002183018.37343c26@harpe.intellique.com>

On Tue, Oct 2, 2018 at 10:30 AM, Emmanuel Florac <eflorac@intellique.com> wrote:
> 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.

Stratis volumes are always built on dm-thin so I'd expect default
mkfs.xfs to create ~33 AG's, which is what I get when running mkfs.xfs
on LVM thin volumes.

-- 
Chris Murphy

  reply	other threads:[~2018-10-04  5:37 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
2018-10-03 22:47       ` Chris Murphy [this message]
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=CAJCQCtQyXjB1bzOWuj8f+cd-WgFkxDY8xpZ8YhVoTC72rPLThA@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=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 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.