All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Farnum <gregory.farnum@dreamhost.com>
To: Sage Weil <sage@newdream.net>
Cc: "Jim Schutt" <jaschut@sandia.gov>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: monitor dispatch queue seems backed up?
Date: Fri, 4 Mar 2011 12:38:03 -0800	[thread overview]
Message-ID: <1C3F2964F2314471949A0E8F6C807216@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103041137050.25280@cobra.newdream.net>

On Friday, March 4, 2011 at 11:48 AM, Sage Weil wrote:
Hi,
> > 
> > I'm continuing my testing of the master branch
> > (commit 1ed2d8c587) against 96 osds.
> > 
> > I'm having trouble getting a new filesystem to
> > start up. FWIW this size filesystem starts up
> > in a minute or two at most under the stable branch.
> 
> The main thing that's changed since then is the default number of PGs has 
> gone up. Can you try changing the osd_pg_bits to 6 in common/config.cc, 
> rebuild, and re-mkcephfs, and see if that gives you behavior similar to 
> stable? (mkcephfs isn't currently letting you adjust that yet.)

Hmmm, I believe that if you set the osd_pg_bits in your ceph.conf it should get picked up by mkcephfs. :) Otherwise there are command-line options, and I have checked to make sure they work!
-Greg




  reply	other threads:[~2011-03-04 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 17:14 monitor dispatch queue seems backed up? Jim Schutt
2011-03-04 19:48 ` Sage Weil
2011-03-04 20:38   ` Gregory Farnum [this message]
2011-03-04 20:46     ` Sage Weil
2011-03-04 20:53     ` Yehuda Sadeh Weinraub
2011-03-04 21:00       ` Gregory Farnum
2011-03-04 20:45   ` Jim Schutt
2011-03-04 22:47   ` Jim Schutt
2011-03-04 23:56     ` Sage Weil
2011-03-07 15:26       ` Jim Schutt

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=1C3F2964F2314471949A0E8F6C807216@gmail.com \
    --to=gregory.farnum@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jaschut@sandia.gov \
    --cc=sage@newdream.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.