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: Mon, 26 Aug 2013 23:28:50 +0200 [thread overview]
Message-ID: <521BC892.40601@gmail.com> (raw)
In-Reply-To: <521BC829.9080303-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> I tried, but with the blkid check first my /dev/bcache* devices are
>> not reliably created. I have 2 in total (/dev/bcache0 and
>> /dev/bcach1) and with the blkid there's only one after any reboot.
>> Although the name varies (bcache0 or bcache1) it actually is always
>> the /dev/bcache* device for the 'second' bcache device that is
>> created. second one means: the first one is the combi of /dev/sda3 &
>> /dev/sdb1, the second one is the combi of /dev/sdc1 and /dev/sdd1.
>> I'm not sure how I can figure out what's actually happening during
>> boot.
>
> Possibly /dev/sdc1 or /dev/sdd1 has a stray non-bcache superblock.
(I mean the other two, your "first" pair)
> You can check with wipefs, and remove it with wipefs -a.
next prev parent reply other threads:[~2013-08-26 21:28 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 [this message]
2013-08-26 22:20 ` Rolf Fokkens
[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=521BC892.40601@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 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.