Comment 9 for bug 1856871
Revision history for this message
| Thadeu Lima de Souza Cascardo (cascardo) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
<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.