From: Marc MERLIN <marc@merlins.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Hard to delete/unregister caching device
Date: Sun, 21 Feb 2016 13:22:05 -0800 [thread overview]
Message-ID: <20160221212205.GB5512@merlins.org> (raw)
In-Reply-To: <20160221041753.GB24735@kmo-pixel>
On Sat, Feb 20, 2016 at 07:17:53PM -0900, Kent Overstreet wrote:
> > bcache0 is fine
> > bcache1 ended up in a bad state, I'm not sure how.
> > No biggie, right, just delete/recreate/re-register sda6, except how?
> >
> > https://www.kernel.org/doc/Documentation/bcache.txt
> > SYSFS - CACHE DEVICE:
> > says nothing about how I can free/release sda6
> >
> > saruman:~# echo /dev/sda6 > /sys/fs/bcache/unregister
> > -su: /sys/fs/bcache/unregister: Permission denied
> > is not helpful, nothing in kern.log
>
> echo 1 > /sys/fs/bcache/<uuid>/unregister
If you look lower down in my Email, I did do almost the same:
saruman:/sys/fs/bcache/f419195d-184e-44b7-9f88-a834a5458f8c# echo 1 > stop
I was pointing out that for a newcomer, it's not all super obvious how
all the pieces fit together.
Is https://www.kernel.org/doc/Documentation/bcache.txt still considered
the canonical documentation?
I could try writing some kind of howto update for it if so.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2016-02-21 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 6:48 Hard to delete/unregister caching device Marc MERLIN
2016-02-21 4:17 ` Kent Overstreet
2016-02-21 21:22 ` Marc MERLIN [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-24 19:13 Eric Wheeler
2016-02-24 21:30 ` Marc MERLIN
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=20160221212205.GB5512@merlins.org \
--to=marc@merlins.org \
--cc=kent.overstreet@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.