From: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
To: Dan Mick <dan.mick@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: librbd: error finding header
Date: Mon, 09 Jul 2012 19:59:07 +0930 [thread overview]
Message-ID: <4FFAB273.6030605@bashkirtsev.com> (raw)
In-Reply-To: <4FFA9E6D.7030207@inktank.com>
On 09/07/12 18:33, Dan Mick wrote:
> Vladimir: you can do some investigation with the rados command. What
> does
> rados -p rbd ls show you?
Rather long list of:
rb.0.11.000000002786
rb.0.d.0000000054a2
rb.0.6.000000002eb5
rb.0.d.000000008294
rb.0.13.000000000377
rb.0.e.000000000629
rb.0.6.000000002756
rb.0.d.000000006156
rb.0.d.000000009b82
rb.0.5.000000000c9e
rb.0.d.0000000080ba
rb.0.f.000000000e75
rb.0.6.00000000ab4f
rb.0.d.0000000048e4
rb.0.d.000000005f67
rb.0.13.0000000014ad
rb.0.d.00000000e074
rb.0.f.000000001a4b
rb.0.13.0000000004a3
...
How to find out to which image these objects belong?
>
> On 07/08/2012 10:42 PM, Vladimir Bashkirtsev wrote:
>> Hello,
>>
>> I just hit this error:
>>
>> error opening image sip.logics.net.au: (2) No such file or directory
>> 2012-07-09 15:03:59.935835 7ffbe0673780 -1 librbd: error finding
>> header: (2) No such file or directory
>>
>> Googled around and found that Oliver Francke had similar issue back
>> in March. Read your responses but still unclear where to start to
>> dig. Just upgraded from 0.47.3 to 0.48, done rolling upgrade and all
>> RBD images are OK with exception of this one. Notably as upgrade was
>> done while VM was up it continued to run unaffected (ie all data
>> inside of VM was written and read as nothing happened). It makes me
>> think that there no data loss but mere broken header.
>>
>> Of course I have a backup of VM and can pull it back in no time but I
>> am really interested (and I am sure other ceph users) how to recover
>> from such failures?
>>
>> Regards,
>> Vladimir
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2012-07-09 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 5:42 librbd: error finding header Vladimir Bashkirtsev
2012-07-09 9:03 ` Dan Mick
2012-07-09 10:29 ` Vladimir Bashkirtsev [this message]
2012-07-09 16:30 ` Florian Haas
2012-07-10 3:28 ` Vladimir Bashkirtsev
2012-07-09 17:47 ` Dan Mick
2012-07-10 3:29 ` Vladimir Bashkirtsev
[not found] ` <4FFBA108.3010009@bashkirtsev.com>
[not found] ` <4FFBB74F.2050702@inktank.com>
2012-07-10 9:25 ` Vladimir Bashkirtsev
2012-07-10 20:08 ` Josh Durgin
2012-07-12 2:40 ` Vladimir Bashkirtsev
2012-07-12 4:41 ` Josh Durgin
2012-07-12 16:00 ` Tommi Virtanen
2012-07-13 13:06 ` Vladimir Bashkirtsev
2012-07-14 0:34 ` Josh Durgin
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=4FFAB273.6030605@bashkirtsev.com \
--to=vladimir@bashkirtsev.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox