Hi-- sorry you are having trouble.. On 10/12/2017 05:49 AM, Alexandr Kuznetsov wrote: > Hellow. > > Can any one help me? Two days ago i encountered bcache failure and since > then i can't boot my system Ubuntu 16.04 amd64. > Now when cache and backend devices meets each other during register > process, something hangs inside the kernel and such messages appear in > dmesg: [snip] > 54 backing devices show: > dev.data.cache_mode 1 [writeback] > dev.data.cache_state 1 [clean] > cset.uuid d93ae507-b4bb-48ef-8d64-fa9329a08a39 > One backing device (md0p3) show: > dev.data.cache_mode 1 [writeback] > dev.data.cache_state 1 [dirty] > cset.uuid d93ae507-b4bb-48ef-8d64-fa9329a08a39 > And one strange device (md0p2) show: > dev.data.cache_mode 1 [writeback] > dev.data.cache_state 0 [detached] > cset.uuid 9a6aeb43-5f33-45ca-a1b0-a1277e3e5c44 It looks like probably the superblock of md0p2 and other data structures were corrupted during the lvm commands, and in turn this is triggering bugs with bcache (bcache should detect the situation and abort everything, but instead is left with the bucket_lock held and freezes). One thing you could do possibly do is blacklist bcache in your /etc/modules, and then attach all the devices one by one, (not including md0p2), to get at the data on all the other volumes. Also, 54 of the backing devices are clean-- they have no dirty data in the cache-- so they can be mounted directly if you want. Mike -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
