• [6.9.0] (and previous releases)] a corrupted file on a btrfs filesyem doesn't return -EIO when user shares are used

    • Minor

    Found out recently that when reading a corrupt btrfs file using user shares the transfer doesn't abort with an IO error as it should, this is similar to what happened before with Samba AIO enable, but in this case it also affects local transfers, when using disk shares it works as it's supposed to, I never caught this before since I always tested with disk shares, it goes back to at least v6.6, which is the oldest release I tried.


    At first I though it would be related to having direct IO enable, but I'm seeing the same with direct IO disable, I know of this issue occurring when O_DIRECT is used, does FUSE use that or anything similar?


    This isn't a big deal since data corruption (on good hardware) is extremely rare and there other ways of monitoring for corruption, still it would be nice if it worked as it should.




    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.