From: Fyodor Ustinov <ufm@ufm.su>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: ceph-devel@vger.kernel.org, samuel.just@dreamhost.com
Subject: Re: inconsistent chunk
Date: Sat, 18 Jun 2011 18:27:42 +0300 [thread overview]
Message-ID: <4DFCC3EE.2090700@ufm.su> (raw)
In-Reply-To: <E58F9FF9-B13F-45D7-86D3-5C1940A919C7@dreamhost.com>
On 06/17/2011 07:27 PM, Gregory Farnum wrote:
> 4. Can I recover the data without backup?
> Possibly. If the inconsistency is just that one of the OSDs is storing the object and another OSD says the object shouldn't exist, that can be recovered from by working out which one is correct.
>
> Have you manually adjusted the contents of any OSDs? Can you think of anything you've done that might have triggered this?
I step by step down osd servers until only one remains (hmm, it is not
clear how this is consistent with "pg_size 2"). After one day I step by
step up osd servers.
WBR,
Fyodor.
next prev parent reply other threads:[~2011-06-18 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 5:20 inconsistent chunk Fyodor Ustinov
2011-06-17 16:27 ` Gregory Farnum
2011-06-18 15:27 ` Fyodor Ustinov [this message]
2011-06-20 17:16 ` Gregory Farnum
2011-06-20 17:19 ` Fyodor Ustinov
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=4DFCC3EE.2090700@ufm.su \
--to=ufm@ufm.su \
--cc=ceph-devel@vger.kernel.org \
--cc=gregory.farnum@dreamhost.com \
--cc=samuel.just@dreamhost.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.