All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <dchinner@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: David Casier <david.casier@aevoo.fr>,
	Ric Wheeler <rwheeler@redhat.com>, Sage Weil <sage@newdream.net>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	Brian Foster <bfoster@redhat.com>
Subject: Re: Fwd: Fwd: [newstore (again)] how disable double write WAL
Date: Tue, 23 Feb 2016 16:20:21 +1100	[thread overview]
Message-ID: <20160223052021.GH2005@devil.localdomain> (raw)
In-Reply-To: <56CB346B.50200@redhat.com>

On Mon, Feb 22, 2016 at 10:16:43AM -0600, Eric Sandeen wrote:
> On 2/22/16 10:12 AM, David Casier wrote:
> > I have carried out tests very quickly and I have not had time to
> > concentrate fully on XFS.
> >  maxpct =0.2 => 0.2% of 4To = 8Go
> > Because my existing ssd partitions are small
> > 
> > If i'm not mistaken, and with what Dave says :
> > By default, data is written to 2^32 inodes of 256 bytes (= 1TiB).
> > With maxpct, you set the maximum size used by inodes, depending on the
> > percentage of disk

maxpct doesn't work like that. It's a limit on the count of inodes,
not a limit on their physical location.

And, FWIW, mkfs does not take floating point numbers, so that
mkfs.xfs command line is not doing what you think it's doing. In
fact, it's probably setting maxpct to zero, and the kernel is then
ignoring it because it's invalid.

Cheers,

Dave.
-- 
Dave Chinner
dchinner@redhat.com

      parent reply	other threads:[~2016-02-23  5:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9D046674-EA8B-4CB5-B049-3CF665D4ED64@aevoo.fr>
2015-11-24 20:42 ` Fwd: [newstore (again)] how disable double write WAL Sage Weil
     [not found]   ` <CA+gn+znHyioZhOvuidN1pvMgRMOMvjbjcues_+uayYVadetz=A@mail.gmail.com>
2015-12-01 20:34     ` Fwd: " David Casier
2015-12-01 22:02       ` Sage Weil
2015-12-04 20:12         ` Ric Wheeler
2015-12-04 20:20           ` Eric Sandeen
2015-12-08  4:46           ` Dave Chinner
2016-02-15 15:18             ` David Casier
2016-02-15 16:21               ` Eric Sandeen
2016-02-16  3:35               ` Dave Chinner
2016-02-16  8:14                 ` David Casier
2016-02-16  8:39                   ` David Casier
2016-02-19  5:26                     ` Dave Chinner
2016-02-19 11:28                       ` Blair Bethwaite
2016-02-19 12:57                         ` Mark Nelson
2016-02-22 12:01                       ` Sage Weil
2016-02-22 17:09                         ` David Casier
2016-02-22 17:16                           ` Sage Weil
2016-02-18 17:54                 ` David Casier
2016-02-19 17:06                 ` Eric Sandeen
2016-02-21 10:56                   ` David Casier
2016-02-22 15:56                     ` Eric Sandeen
2016-02-22 16:12                       ` David Casier
2016-02-22 16:16                         ` Eric Sandeen
2016-02-22 17:17                           ` Howard Chu
2016-02-23  5:20                           ` Dave Chinner [this message]

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=20160223052021.GH2005@devil.localdomain \
    --to=dchinner@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=david.casier@aevoo.fr \
    --cc=rwheeler@redhat.com \
    --cc=sage@newdream.net \
    --cc=sandeen@redhat.com \
    /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.