From: Kai Krakow <hurikhan77@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Re: disk gone
Date: Sat, 10 Jun 2017 12:17:22 +0200 [thread overview]
Message-ID: <20170610121722.124dbfc0@jupiter.sol.kaishome.de> (raw)
In-Reply-To: alpine.LRH.2.11.1706090144550.19359@mail.ewheeler.net
Am Fri, 9 Jun 2017 01:46:24 +0000 (UTC)
schrieb Eric Wheeler <bcache@lists.ewheeler.net>:
> On Fri, 2 Jun 2017, feng D wrote:
>
> > hi:
> >
> > Some time, the online machine will appear disk gone situation,
> > although this is not very common, but we have too many machines, so
> > still will encounter it.
> >
> > That in the case of disk gone, /sys/block/bcache0/bcache/stop is
> > not found, this case how to delete the bcache0?
>
> An interesting question. Is it still available from the cache device
> in /sys/fs/bcache/* somewhere? I'm guessing not, but check.
>
> Do you have a procedure to reproduce this problem
> where /sys/block/bcache0 has been hotplugged into oblivion?
You easily run into the same situation when you stop the device instead
of detaching it. Bcache then doesn't release its cache device and
cannot be stopped/unregistered, because every interface for shutting
bcache down has vanished: It can only be reached through the backing
devices but the bcache interface below those is gone.
I think bcache needs a way to force unregister the cache device...
Otherwise the cache device stays busy and cannot be registered, neither
can any devices be attached again in this state.
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2017-06-10 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 9:31 disk gone feng D
2017-06-09 1:46 ` Eric Wheeler
2017-06-10 10:17 ` Kai Krakow [this message]
2017-06-14 0:24 ` Eric Wheeler
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=20170610121722.124dbfc0@jupiter.sol.kaishome.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox