• [6.10.0-rc5] SSD Cache TRIM (discard=async) not working

    Devifish

    By Devifish

      • Minor

    SSD Cache TRIM (discard=async) not working

    btrfs not use discard=async

     

    log:

    image.thumb.png.9d5d38d536eb1e9e28ecad3a6d2c7d06.png

     

    mount:

    image.thumb.png.882bccea4d0f4c63a4a7056c4b52fd59.png

     

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    JorgeB

    For now it's only enable for pools, you can have a single device "pool" as long as pool slots are set to >1, though I agree it should be enabled for everything.

    Link to comment
    limetech
    7 hours ago, JorgeB said:

    For now it's only enable for pools, you can have a single device "pool" as long as pool slots are set to >1, though I agree it should be enabled for everything.

     

    The mount options for a btrfs pool are:

    noatime,space_cache=v2,discard=async

     

    We can apply those same options to a btrfs unRAID device - would be better?

    Link to comment
    JorgeB
    48 minutes ago, limetech said:

    We can apply those same options to a btrfs unRAID device - would be better?

    Yes, you can enable for all btrfs pool devices, for array devices I assume discard would still be blocked for any md device like fstrim currently is, or it would make parity out of sync if SSDs are used in the array?

    Link to comment


    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.

    Guest
    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.