------- Comment From [email protected] 2019-04-02 04:03 EDT------- (In reply to comment #12) > @Peter > I guess the question is, whether or not, we should be trying to use dasd as > a bcache device at all.
In my opinion completely preventing the use of DASD for bcache would be overly restrictive. > Or like create a partition table, and use the > partition as a bcache device then? In that case should the make-bcache fail > on the full dasd device, as shows in the reproducer steps? Creating a partition and using the partition as bcache device is the recommended approach. I don't think that workarounds for DASD particularities would fit into bcache-tools though. > If I understand correctly where the request is coming from, > MAAS/NewServerInstaller use curtin which supports bcache setup, and that > fails with dasd drives at the moment in curtin's implementation / > integration test suite. I'm not familiar with curtin, but if that's a layer on top that makes use of bcache-tools, then that may be a good place to catch/prevent the attempt to run bcache on the DASD block device and to suggest using a partition instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
