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: Fri, 6 Dec 2013 17:57:13 +0000 [thread overview]
Message-ID: <20131206175712.GD23496@debian> (raw)
In-Reply-To: <20131206154914.GE25206@samfundet.no>
On Fri, Dec 06, 2013 at 04:49:14PM +0100, Steinar H. Gunderson wrote:
> Linux (3.12.0-rc5) hung, and on boot, I can't get the dm-cache up again:
>
> (initramfs) echo 0 23440891904 cache /dev/cache/metadata /dev/cache/blocks /dev/md1 1024 1 writeback
> default 4 random_threshold 8 sequential_threshold 512 | dmsetup create cache -u CACHE-0a8bb56fc873c195bf7117af925c7f08
> device-mapper: reload ioctl on cache failed: Input/output error
> Command failed
>
> The kernel complains with
>
> [ 639.189756] attempt to access beyond end of device
> [ 639.189761] dm-0: rw=0, want=18445688752888627208, limit=1048576
> [ 639.189764] device-mapper: transaction manager: couldn't open metadata space map
> [ 639.189767] device-mapper: cache metadata: tm_open_with_sm failed
> [ 639.283130] device-mapper: table: 254:2: cache: Error creating metadata object
> [ 639.283134] device-mapper: ioctl: error adding target to table
>
> Is there anything I can do short of nuking the metadata partition
> and taking the loss of whatever wasn't written back?
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.
Let me know how it goes,
- Joe
next prev parent reply other threads:[~2013-12-06 17:57 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 [this message]
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
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=20131206175712.GD23496@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.