All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
To: Thierry <thierry-gY9mk9TZ+INg9hUCZPvPmw@public.gmane.org>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bad btree header at bucket xxx.
Date: Sat, 09 Nov 2013 11:37:23 +0100	[thread overview]
Message-ID: <527E1063.4090209@rolffokkens.nl> (raw)
In-Reply-To: <5276DE9D.6000401-gY9mk9TZ+INg9hUCZPvPmw@public.gmane.org>

On 11/04/2013 12:39 AM, Thierry wrote:
> After a reboot, the bcache devices didn't appeared. Looking at dmesg I
> foud out the following entries:
> [ 12.182288] bcache: register_bdev() registered backing device dm-0
> [ 12.217379] bcache: register_bdev() registered backing device dm-1
> [ 12.253040] bcache: error on d8e791cc-47c2-449c-909a-1e4433a5de11: bad
> btree header at bucket 32018, block 0, 0 keys, disabling caching
> [ 12.253050] bcache: register_cache() registered cache device sdb1
> [ 12.253488] bcache: cache_set_free() Cache set
> d8e791cc-47c2-449c-909a-1e4433a5de11 unregistered
>
> As you see I restarted the devices after having changed the cache mode
> to "none" followed by a echo 1 > running (The state of the 2 devices
> were dirty)
> e2fsck do not report any problem on any of the bcache device
>
> Are there other "emegency actions" I should take (cache is till reported
> as inconsistent)?
I've seen the same problems in earlier kernels, but not in kernels > 3.11.5.

After also forcing the bcache device to running (echo 1 > running) I 
also recreated the caching device (make-bcache -C ...) and reattached it 
to the bcache device. Have you tried to do that?

Rolf

  parent reply	other threads:[~2013-11-09 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 23:39 bad btree header at bucket xxx Thierry
     [not found] ` <5276DE9D.6000401-gY9mk9TZ+INg9hUCZPvPmw@public.gmane.org>
2013-11-09  8:47   ` Thierry De Leeuw
2013-11-09 10:37   ` Rolf Fokkens [this message]
     [not found]     ` <527E1063.4090209-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-11-09 13:00       ` Thierry De Leeuw
     [not found]         ` <527E31DF.5080204-gY9mk9TZ+INg9hUCZPvPmw@public.gmane.org>
2013-11-10 10:09           ` Rolf Fokkens
     [not found]             ` <527F5B57.1020400-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-11-10 15:16               ` Thierry De Leeuw

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=527E1063.4090209@rolffokkens.nl \
    --to=rolf-6w2rdlbueqtpmfipwq+h6g@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry-gY9mk9TZ+INg9hUCZPvPmw@public.gmane.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.