From: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
To: Tobias Reinhard <trtracer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Error "unsupported bset version"
Date: Mon, 26 Aug 2013 15:10:09 -0700 [thread overview]
Message-ID: <20130826221009.GH2798@kmo-pixel> (raw)
In-Reply-To: <52189D62.7010603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Sat, Aug 24, 2013 at 01:47:46PM +0200, Tobias Reinhard wrote:
> Hi all,
>
> I'm running bcache to speed up my 4 TB HDD with a 64 GB partition on
> my SSD. After a reboot bcache didn't start automatically. So I
> stopped bcache, unloaded the module, reloaded it and tried to
> register the SSD and HDD again.
>
> Registering the SSD gave me this error:
> error on f1e69e99-940d-447a-900e-4956bd607933: unsupported bset
> version at bucket 108098, block 0, 855650560 keys, disabling caching
>
> The bcache was running in writeback mode but I think it was almost
> clean so I forced the device to go online and made an fsck.
> Everything looks ok, so no data loss. But surely this should not
> happen, right? Is there any way to check why? (I made an image of
> the cache device)
I think this was the result of a bug for which I accidentally didn't
mark the fix for stable - the fix was in 3.11
I just sent out a pull request to get it into 3.10, and in the meantime
I have a branch with all the relevant fixes on top of 3.10:
git://evilpiepirate.org/~kent/linux-bcache.git bcache-3.10-stable
prev parent reply other threads:[~2013-08-26 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 11:47 Error "unsupported bset version" Tobias Reinhard
[not found] ` <52189D62.7010603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-26 22:10 ` Kent Overstreet [this message]
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=20130826221009.GH2798@kmo-pixel \
--to=kmo-pezghdh756f8ursed/g0lq@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trtracer-Re5JQEeQqe8AvxtiuMwx3w@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.