From: Greg Farnum <gregory.farnum@dreamhost.com>
To: Damien Churchill <damoxc@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: pgs stuck inactive
Date: Thu, 19 Apr 2012 10:09:23 -0700 [thread overview]
Message-ID: <ACEFADB1EB0E4549BE3E5383B36B9437@dreamhost.com> (raw)
In-Reply-To: <CAFtEh-e9XEhXiaoC-uwv1x6w1OmqEmXW8b6Y8Hcp0E+O0-smRg@mail.gmail.com>
On Thursday, April 19, 2012 at 2:07 AM, Damien Churchill wrote:
> On 18 April 2012 21:41, Greg Farnum <gregory.farnum@dreamhost.com (mailto:gregory.farnum@dreamhost.com)> wrote:
> > 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.)
>
>
>
> Thanks a lot Greg!
>
> All back up and running now. What negative side effects could having
> the pools mixed together have, given that I'm not doing any special
> placement of them?
There shouldn't be any negative side effects from it at all. It just means that you've got a mixed namespace, and if you don't care about that none of our current tools do either. (Something like the still-entirely-theoretical ceph-fsck probably wouldn't appreciate it, but we don't have anything like that right now.)
prev parent reply other threads:[~2012-04-19 17:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 8:12 pgs stuck inactive Damien Churchill
2012-04-04 20:51 ` Samuel Just
2012-04-04 21:44 ` Damien Churchill
2012-04-06 16:50 ` Samuel Just
2012-04-06 16:55 ` Damien Churchill
2012-04-06 17:30 ` Samuel Just
2012-04-06 17:53 ` Damien Churchill
[not found] ` <CACLRD_3hqoOqbZWnyft3B+pEaPG=pmiDt5HeQASUC=OPS-uA7Q@mail.gmail.com>
[not found] ` <CAFtEh-dnR0zu=ct-gG0L+76BTYHVFimjFKNhHjnDNZWA=Scs1g@mail.gmail.com>
2012-04-06 18:20 ` Samuel Just
[not found] ` <CAFtEh-cx2by6yG_xiQbq5e2fbViOWyHoaOLFPBCZgX7x-7gwFA@mail.gmail.com>
[not found] ` <CACLRD_0UrwKJuELiZqrL7Q_5AjB1EvOd5gqLRzrxw_7AFMcjxg@mail.gmail.com>
[not found] ` <CAFtEh-fwt9BwZ7NwZaJVnwq3hgzvkrb1XvKT0uF81vePRcu7oA@mail.gmail.com>
2012-04-10 21:49 ` Samuel Just
2012-04-10 22:03 ` Damien Churchill
2012-04-10 23:00 ` Samuel Just
2012-04-10 23:40 ` Greg Farnum
2012-04-12 15:29 ` Damien Churchill
2012-04-13 19:30 ` Greg Farnum
2012-04-13 19:42 ` Damien Churchill
2012-04-17 0:06 ` Greg Farnum
2012-04-17 5:32 ` Damien Churchill
2012-04-17 16:49 ` Greg Farnum
2012-04-18 4:35 ` Martin Wilderoth
2012-04-18 6:41 ` Damien Churchill
2012-04-18 18:41 ` Greg Farnum
2012-04-18 19:04 ` Damien Churchill
2012-04-18 20:41 ` Greg Farnum
2012-04-19 9:07 ` Damien Churchill
2012-04-19 17:09 ` Greg Farnum [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=ACEFADB1EB0E4549BE3E5383B36B9437@dreamhost.com \
--to=gregory.farnum@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=damoxc@gmail.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.