All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
To: ceph-devel@vger.kernel.org
Subject: librbd: error finding header
Date: Mon, 09 Jul 2012 15:12:13 +0930	[thread overview]
Message-ID: <4FFA6F35.4040102@bashkirtsev.com> (raw)

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

             reply	other threads:[~2012-07-09  5:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  5:42 Vladimir Bashkirtsev [this message]
2012-07-09  9:03 ` librbd: error finding header Dan Mick
2012-07-09 10:29   ` Vladimir Bashkirtsev
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=4FFA6F35.4040102@bashkirtsev.com \
    --to=vladimir@bashkirtsev.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.