public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf@rolffokkens.nl>
To: Slava Pestov <sp@datera.io>, "Stephen R. van den Berg" <srb@cuci.nl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: 3.18.1 + latest bcache-dev
Date: Sat, 03 Jan 2015 17:40:24 +0100	[thread overview]
Message-ID: <54A81B78.2070409@rolffokkens.nl> (raw)
In-Reply-To: <CACHGV4K8aK8=isPftZLsMHCqUf31t1B=kFXDUD1PFCKzDC-D=g@mail.gmail.com>

Hi Slava,

Sounds like the kernel (using bcache-dev) is not able to handle the 
current format. If so, bcache-tools may help in "reformatting" bcache 
devices, but that's no solution for existing systems.

So is my understanding correct that there's no easy kernel upgrade path 
(to bcache-dev) ?

Rolf

On 12/29/2014 05:05 AM, Slava Pestov wrote:
> Hi Stephen,
>
> The bcache-dev branch has on-disk format changes that require a new
> bcache-tools. I'm not sure where Kent posts the source for that.
>
> On Sat, Dec 27, 2014 at 6:35 PM, Stephen R. van den Berg <srb@cuci.nl> wrote:
>> Now I tried this:
>> Combine 3.18.1 and rebase all the patches from bcache-dev onto that.
>> But, in trying that, I get a consistent:
>>
>> register_bcache() error opening /dev/sdb3: Invalid superblock: member info area missing
>>
>> Anything I overlooked?   The bcache-tools are straight from git too.
>> --
>> Stephen.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-01-03 16:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28  2:35 3.18.1 + latest bcache-dev Stephen R. van den Berg
2014-12-29  4:05 ` Slava Pestov
2015-01-03 16:40   ` Rolf Fokkens [this message]
2015-01-04  0:46     ` Kent Overstreet
2015-01-04 14:11       ` Rolf Fokkens
2015-01-05  7:47         ` Slava Pestov
2015-01-06 22:18           ` Rolf Fokkens
2015-01-06 22:47             ` Slava Pestov
2015-01-07  1:48             ` Kent Overstreet
2015-01-07 17:41               ` Jianjian Huo
2015-01-08  2:29                 ` Kent Overstreet
2015-01-07 20:17             ` Eric Wheeler
2015-01-08  2:30               ` Kent Overstreet
2015-01-08 19:47                 ` Rolf Fokkens
2015-01-05  8:49       ` Stephen R. van den Berg
2015-01-05 11:06         ` Kent Overstreet
2015-01-06  9:16           ` Stephen R. van den Berg
2015-01-06 11:10             ` Kent Overstreet

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=54A81B78.2070409@rolffokkens.nl \
    --to=rolf@rolffokkens.nl \
    --cc=linux-bcache@vger.kernel.org \
    --cc=sp@datera.io \
    --cc=srb@cuci.nl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox