Re: pgs stuck inactive

[Greg Farnum <gregory.farnum@dreamhost.com>]

On Wednesday, April 18, 2012 at 12:04 PM, Damien Churchill wrote:
> On 18 April 2012 19:41, Greg Farnum <gregory.farnum@dreamhost.com (mailto:gregory.farnum@dreamhost.com)> wrote:
> > 
> > Are you building your binaries from source, and can you run a patched version of the monitors? If you can I'll give you a patch to enable a simple command that should make things work; otherwise we'll need to start editing things by hand. (Yucky)
> > -Greg
> 
> 
> 
> I was using the Ubuntu packages but I can quite happily build my own
> packages if you give me the patch :-)
> 
> I agree it's a waste of time if it's not obvious what's caused it,
> could be some obscure cause occurred due to upgrading between older
> versions.

Okay, assuming you're still on 0.41.1, can you checkout the git branch "for-damien" and build it? 
Then shut down your monitors, replace their executables with the freshly-built ones, and run
"ceph osd pool set vmimages pg_num 320 --a-dev-told-me-to"
and
"ceph osd pool set vmimages pgp_num 320"



That should get everything back up and running. The one sour note is that due to the bug in the past, your data (ie, filesystem) and vmimages pools have gotten conflated. It shouldn't cause any issues (they use very different naming schemes), but they're tied together in terms of replication and the raw pool statistics.
(If that's important you can create a new pool and move the rbd images to it.)
-Greg