public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
To: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache-tools: changes to make the udev rules work
Date: Tue, 27 Aug 2013 00:20:06 +0200	[thread overview]
Message-ID: <521BD496.5060207@rolffokkens.nl> (raw)
In-Reply-To: <521BC829.9080303-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 08/26/2013 11:27 PM, Gabriel de Perthuis wrote:
> Possibly /dev/sdc1 or /dev/sdd1 has a stray non-bcache superblock.
You're right, see below. That was an ugly one.

Do you think having blkid identify bcache itself would have helped, or 
is there always a chance of contradictive signatures which may confuse  
blkid?
>
> You can check with wipefs, and remove it with wipefs -a.
The evidence:

[root@localhost ~]# wipefs /dev/sda3
[root@localhost ~]# wipefs /dev/sdb1
offset               type
----------------------------------------------------------------
0x218                LVM2_member   [raid]
                      UUID:  ZSSjZv-FU0H-Zeaa-92GU-37Zs-KyLS-JMF03Y

[root@localhost ~]# wipefs /dev/sdc1
[root@localhost ~]# wipefs /dev/sdd1
[root@localhost ~]# blkid /dev/sdb1
/dev/sdb1: UUID="ZSSjZv-FU0H-Zeaa-92GU-37Zs-KyLS-JMF03Y" TYPE="LVM2_member"
[root@localhost ~]#

  parent reply	other threads:[~2013-08-26 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  9:23 bcache-tools: changes to make the udev rules work Rolf Fokkens
2013-08-26 15:27 ` Gabriel de Perthuis
2013-08-26 21:01   ` Rolf Fokkens
     [not found]     ` <521BC237.9000802-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-26 21:27       ` Gabriel de Perthuis
     [not found]         ` <521BC829.9080303-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-26 21:28           ` Gabriel de Perthuis
2013-08-26 22:20           ` Rolf Fokkens [this message]
     [not found]             ` <521BD496.5060207-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-26 22:46               ` Gabriel de Perthuis
     [not found] <1377516018.51534.YahooMailAndroidMobile@web181503.mail.ne1.yahoo.com>
     [not found] ` <95A9778F-C617-4455-BBEC-23F0DB06072C@rolffokkens.nl>
     [not found]   ` <95A9778F-C617-4455-BBEC-23F0DB06072C-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-27  0:17     ` matthew patton

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=521BD496.5060207@rolffokkens.nl \
    --to=rolf-6w2rdlbueqtpmfipwq+h6g@public.gmane.org \
    --cc=g2p.code-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox