From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sage@inktank.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Tommi Virtanen <tv@inktank.com>,
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 13:24:06 -0400 [thread overview]
Message-ID: <20120703172406.GA4916@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1207030959320.28638@cobra.newdream.net>
On Tue, Jul 03, 2012 at 10:09:33AM -0700, Sage Weil wrote:
> The OSD keeps directories small on its own by breaking the contents of
> large directories into smaller subdirectories.
Right, that's what I remembered. At least for XFS that'll actually
give you much worse allocation patters as each new directory rotates
to a new allocation group.
> That said, on one system we did see what looked like crazy bad
> fragmentation on an XFS directory... it had maybe 5 subdirs in it and many
> many blocks. That was probably shortly after it had been big and rehashed
> its contents into the subdirs. Yehuda probably remembers more.
Another reason why not doing the artifical directories is better...
> In any case, is there a way to prod XFS into defragging a specific
> directory?
No. XFS can only defragment regular files at the moment.
prev parent reply other threads:[~2012-07-03 17:24 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
2012-07-03 17:04 ` Gregory Farnum
2012-07-03 17:09 ` Sage Weil
2012-07-03 17:24 ` Christoph Hellwig [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=20120703172406.GA4916@infradead.org \
--to=hch@infradead.org \
--cc=David.Blundell@100percentit.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--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.