While the interface is annoying, it *is* possible to have bcache let go
of both backing store and cache devices via the sysfs interfaces.
** Changed in: bcache-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Thanks,
I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was
only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I
was left with an used device.
I agree that the interface is not very user-fiendly, we may need to
improve the bcache-tools command to simplify
Ok, but that leaves sda in a state which looks unclaimed but is still in
use.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1377142
Title:
Bcache doesn't allow full unregister
which can be fixed by unregistering via /sys/fs/bcache... what a
horrible interface.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1377142
Title:
Bcache doesn't allow full unr
Interesting note: "echo 1 >/sys/block/bcache0/bcache/stop" from a point
where the bcache is registered and running (but not mounted) directly
releases both devices for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in
# umount /mnt
# echo 1 >/sys/fs/bcache/a8f70bd1-48df-462f-9a2c-ca4b8af9059c/unregister
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 16G 0 disk
sdb 8:16 08G 0 disk
└─bcache0 251:008G 0 disk
# echo 1 >/sys/block/bcache0/bcache/stop
# lsblk
N
Hm, it was helping in my case. So here from my re-run with utopic KVM
host:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 16G 0 disk
└─bcache0 251:008G 0 disk /mnt
sdb 8:16 08G 0 disk
└─bcache0 251:008G 0 disk /mnt
# bcache-super-
In fact whether you unmount before stopping the bcache or not doesn't
change the behaviour. I did that this way in the description, to show
the process. You just stop the caching device with the echo 1 > ...
But, the backing is still in use, but you have no control over it.
Le 08/10/2014 13:15, St
Yes you can get rid of bcache0, but you can't re-use the device for
anything unless you reboot ( re bcache or just plain fdisk/parted ).
Le 08/10/2014 13:15, Stefan Bader a écrit :
> There does not seem to be clear documentation on this. Just a note that from
> your description I was not complete
There does not seem to be clear documentation on this. Just a note that from
your description I was not completely sure whether you did unmount before
starting the release procedure. I would say unmount is a must.
Doing so, I also ended up in the state where bcache0 still existed. But I was
able
bug 1377130 is the other bug referenced by this one
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1377142
Title:
Bcache doesn't allow full unregistering without rebooting
To
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Description changed:
If you create a bcache device, you can't reuse all your disk/partitions
without a reboot.
You can reproduce the case this way:
start a vm with 2 disks (caching must be bigger or equal to the backing
cf bug :1377130) and an iso of utopic desktop amd64
cr
13 matches
Mail list logo
