From: Nix <nix@esperi.org.uk>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: make-bcache bug?
Date: Mon, 15 May 2017 13:52:09 +0100 [thread overview]
Message-ID: <8737c6th8m.fsf@esperi.org.uk> (raw)
In-Reply-To: <20170514232816.79c2530e@jupiter.sol.kaishome.de> (Kai Krakow's message of "Sun, 14 May 2017 23:28:16 +0200")
On 14 May 2017, Kai Krakow said:
> I had done this previously, too, and had no such message. But I had to
> use wipefs anyway because otherwise udev came and triggered the device
> for reasons I couldn't really follow.
udev does a blkid to see how the block device needs to be activated:
this relies on precisely the information wipefs removes. Avoiding this
problem is why wipefs *exists*. :)
--
NULL && (void)
next prev parent reply other threads:[~2017-05-15 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 17:58 make-bcache bug? Marc MERLIN
2017-05-14 18:01 ` Marc MERLIN
2017-05-14 18:12 ` Still have a problem registering cache devices without rebooting :( Marc MERLIN
2017-05-14 20:00 ` make-bcache bug? Kai Krakow
2017-05-14 20:19 ` Marc MERLIN
2017-05-14 21:28 ` Kai Krakow
2017-05-15 12:52 ` Nix [this message]
2017-05-15 18:37 ` Kai Krakow
2017-05-16 0:58 ` Marc MERLIN
2017-05-16 2:02 ` Kai Krakow
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=8737c6th8m.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=hurikhan77@gmail.com \
--cc=linux-bcache@vger.kernel.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.