From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@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:46:00 +0200 [thread overview]
Message-ID: <521BDAA8.5090803@gmail.com> (raw)
In-Reply-To: <521BD496.5060207-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
> 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?
make-bcache should use libblkid to detect existing superblocks,
and bail and recommend wipefs.
Support in the other direction (having libblkid support bcache) is just a
nice-to-have, and will maybe allow simplifying a few things in bcache-progs.
The udev rule is written not to break if libblkid gets bcache support, but
it can't really be simplified, we still want to detect stray superblocks
even if the latest tools can't create them.
next prev parent reply other threads:[~2013-08-26 22:46 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
[not found] ` <521BD496.5060207-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-26 22:46 ` Gabriel de Perthuis [this message]
[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=521BDAA8.5090803@gmail.com \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rolf-6w2rdlBuEQTpMFipWq+H6g@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