All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Chris Murphy <lists@colorremedies.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: Thu, 4 Oct 2018 12:27:00 +0200	[thread overview]
Message-ID: <20181004122639.330a6243@harpe.intellique.com> (raw)
In-Reply-To: <CAJCQCtQyXjB1bzOWuj8f+cd-WgFkxDY8xpZ8YhVoTC72rPLThA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Le Wed, 3 Oct 2018 16:47:05 -0600
Chris Murphy <lists@colorremedies.com> écrivait:

> >
> > 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.
> 

Ah yes, interesting. I've created a 1TB thin volume and mkfs.xfs makes
32 AGs indeed.

-- 
------------------------------------------------------------------------
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 --]

  reply	other threads:[~2018-10-04 17:20 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
2018-10-04 10:27         ` Emmanuel Florac [this message]
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=20181004122639.330a6243@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --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.