<slashd> so the problem is inside the block layer ? More likely the loop driver not undoing something it does when a file is attached to it. But could as well be something related to the multiqueue support, so could still be something in the block layer. Still needs investigation.
Anyway, as this is not exactly a difference in behavior between the next available loop device and other detached loop devices, what is the exact problem this is causing? I don't see why getting EIO for a detached loop device is the wrong behavior here. I agree there is an inconsistency, but I would accept EIO when trying to fsync a detached device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856871 Title: i/o error if next unused loop device is queried To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1856871/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
