All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-cache refusing to come up again after a crash
Date: Mon, 9 Dec 2013 10:28:11 +0000	[thread overview]
Message-ID: <20131209102811.GB26971@debian> (raw)
In-Reply-To: <20131206191605.GA9700@samfundet.no>

On Fri, Dec 06, 2013 at 08:16:05PM +0100, Steinar H. Gunderson wrote:
> On Fri, Dec 06, 2013 at 05:57:13PM +0000, Joe Thornber wrote:
> > Yep, grab:
> > 
> > https://github.com/jthornber/thin-provisioning-tools
> > 
> > build, and then try cache_check on it (which should tell you what's
> > wrong).  Other programs to play with are cache_dump, cache_restore and
> > cache_repair.
> 
> Well, first of all, it doesn't compile, since you use typename outside of
> templates :-) Fixing that is easy, though. But afterwards:

Grr, I thought that was fixed, what version of g++ are you using?

> 
> root@ubuntu:~/thin-provisioning-tools# ./cache_check /dev/md1
> examining superblock
>   superblock is corrupt
>     bad checksum in superblock
> 
> So where do I want to go from there? cache_dump doesn't want to play with the
> superblock because the checksum is bad... do I want cache_repair, then? Do I
> want to take a backup of anything first?

Ouch.  Could you go through what happened please?  Did dm-cache crash,
or did the machine die for some other reason?

- Joe

  parent reply	other threads:[~2013-12-09 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 15:49 dm-cache refusing to come up again after a crash Steinar H. Gunderson
2013-12-06 17:57 ` Joe Thornber
2013-12-06 19:16   ` Steinar H. Gunderson
2013-12-06 19:35     ` Steinar H. Gunderson
2013-12-06 19:53       ` Steinar H. Gunderson
2013-12-07  0:16         ` Steinar H. Gunderson
2013-12-09 10:31       ` Joe Thornber
2013-12-09 10:28     ` Joe Thornber [this message]
2013-12-09 10:34       ` Steinar H. Gunderson

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=20131209102811.GB26971@debian \
    --to=thornber@redhat.com \
    --cc=dm-devel@redhat.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.