Re: bcache device stuck after backing device goes away, then comes back

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2023-07-05 10:10, Corey Hickey wrote:
At this point, using the backing device via bcache seems impossible
without a reboot.
* original bcache device is still active
* can't stop the bcache device, since the backing device has a new name
* the kernel won't give the backing device the old name

Is there any way to recover from this situation without a reboot?

I found that there was still a dm-crypt device active on top of the bcache device.

I did this:

$ sudo cryptsetup remove backup1
Device /dev/bcache1 does not exist or access denied.
Device /dev/bcache1 does not exist or access denied.
Device /dev/bcache1 does not exist or access denied.
$ echo $?
0

After that, power cycling the backing device allowed it to come back as /dev/sdi and auto-register with bcache.

-Corey



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM Kernel]     [Linux Filesystem Development]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux