On Tue, Jul 19, 2016 at 5:19 AM, Stefan Bader <email address hidden>
wrote:
> While I have not found out where exactly things go wrong, I could
> confirm that this is related to ppc64el builds using a 64k page size. I
> build a test kernel with 4k page size and installed it inside the VM.
> With that bcache-super-show will will reflect the correct status after
> activation and also the superblock magic will remain intact when
> breaking the cache and backing device.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1602299
>
> Title:
> bcache is unstable on ppc64el
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602299/+subscriptions
>
This looks relevant:
https:/ /www.redhat. com/archives/ dm-devel/ 2016-June/ msg00015. html
On Tue, Jul 19, 2016 at 5:19 AM, Stefan Bader <email address hidden>
wrote:
> While I have not found out where exactly things go wrong, I could /bugs.launchpad .net/bugs/ 1602299 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1602299/ +subscriptions
> confirm that this is related to ppc64el builds using a 64k page size. I
> build a test kernel with 4k page size and installed it inside the VM.
> With that bcache-super-show will will reflect the correct status after
> activation and also the superblock magic will remain intact when
> breaking the cache and backing device.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> bcache is unstable on ppc64el
>
> To manage notifications about this bug go to:
> https:/
>