All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Tommi Virtanen <tv@inktank.com>
Cc: David Blundell <David.Blundell@100percentit.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Unable to restart Mon after reboot
Date: Tue, 3 Jul 2012 12:53:58 -0400	[thread overview]
Message-ID: <20120703165358.GA12567@infradead.org> (raw)
In-Reply-To: <CADvuQRFkf8gHOknnj5zyRDBivYttC2Z1CCueZeXH5mnk+11fvQ@mail.gmail.com>

On Tue, Jul 03, 2012 at 09:44:38AM -0700, Tommi Virtanen wrote:
> We've seen similar issues with btrfs, and others have reported that
> the large metadata btrfs option helps. We're still compiling
> information, but as of right now I hear best performance tends to
> happen with xfs; however, the lead position tends to shift around a
> lot.

Btw, does anyone know which part of the btrfs metadata is hit hard?
It's been a while that I looked at the OSD code, but IIRC it didn't
create too big directories, does it?  For heavy directory operations
XFS filesystems created using large directorit blocks (mkfs.xfs -n
size=64k) will also provide additional benefits.

Also IIRC the OSDs have a directory per VDI image - for that kind of
usage pattern the -o filestreams mount option of XFS should provide
even more performance advatages.  Either way make sure to mount with
-o inode64, and for not so recent kernels -o delaylog.

  reply	other threads:[~2012-07-03 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23  0:31 Unable to restart Mon after reboot David Blundell
2012-06-23  5:34 ` Dan Mick
2012-06-23  5:48   ` Dan Mick
2012-06-23 10:43     ` David Blundell
2012-06-25 15:58       ` Tommi Virtanen
2012-07-03 16:35         ` David Blundell
2012-07-03 16:44           ` Tommi Virtanen
2012-07-03 16:53             ` Christoph Hellwig [this message]
2012-07-03 17:04               ` Gregory Farnum
2012-07-03 17:09               ` Sage Weil
2012-07-03 17:24                 ` Christoph Hellwig

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=20120703165358.GA12567@infradead.org \
    --to=hch@infradead.org \
    --cc=David.Blundell@100percentit.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tv@inktank.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.