From: Kent Overstreet <kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: i- <itooo-xVucS5mfmt0AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Not a bcache superblock
Date: Mon, 25 Jul 2011 09:16:35 -0700 [thread overview]
Message-ID: <4E2D96E3.8050709@gmail.com> (raw)
In-Reply-To: <loom.20110725T180931-69-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
On 07/25/11 09:14, i- wrote:
> Hi all,
>
> When trying to register a device with bcache, I have the following error message
> : "bcache: error opening /dev/sdb1: Not a bcache superblock"
>
> Digging around showed me the magic number could not be matched, digging a bit
> more I found out that the cache_sb structures are different in the tools code
> and in the kernel code.
>
> There are 3 fields before the magic in the tools' bcache.h but the magic is the
> first field in bcache.c in the linux module code...
>
> Am I out of sync between repos ? (I cloned them both today)
Yeah, I just uploaded a new version of the tools and the matching
version of bcache isn't up yet.
Do a "git checkout HEAD^" in the bcache-tools repo to get a version
that'll work.
>
> Regards
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-25 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 16:14 Not a bcache superblock i-
[not found] ` <loom.20110725T180931-69-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-07-25 16:16 ` Kent Overstreet [this message]
[not found] ` <4E2D96E3.8050709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-25 16:43 ` i-
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=4E2D96E3.8050709@gmail.com \
--to=kent.overstreet-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=itooo-xVucS5mfmt0AvxtiuMwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@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.