Jump to content
  • [7.0.0-beta.1] emailed cron report shows Trim applied to ALL drives, not just SSDs


    interwebtech
    • Solved Minor

    Pretty sure its harmless as the only disks not listed in the error email are SSDs in the cache pool. Is this something that going to be repeated often? Logs attached just in case.

    Ps. I did not initiate the Trim operation. Report came about 2 hours after upgrade to 7.x

    ==========================================
    cron for user root /sbin/fstrim -a -v | logger &> /dev/null

    fstrim: /mnt/disk18: the discard operation is not supported
    fstrim: /mnt/disk17: the discard operation is not supported
    fstrim: /mnt/disk16: the discard operation is not supported
    fstrim: /mnt/disk15: the discard operation is not supported
    fstrim: /mnt/disk14: the discard operation is not supported
    fstrim: /mnt/disk13: the discard operation is not supported
    fstrim: /mnt/disk12: the discard operation is not supported
    fstrim: /mnt/disk11: the discard operation is not supported
    fstrim: /mnt/disk10: the discard operation is not supported
    fstrim: /mnt/disk9: the discard operation is not supported
    fstrim: /mnt/disk8: the discard operation is not supported
    fstrim: /mnt/disk7: the discard operation is not supported
    fstrim: /mnt/disk6: the discard operation is not supported
    fstrim: /mnt/disk5: the discard operation is not supported
    fstrim: /mnt/disk4: the discard operation is not supported
    fstrim: /mnt/disk3: the discard operation is not supported
    fstrim: /mnt/disk2: the discard operation is not supported
    fstrim: /mnt/disk1: the discard operation is not supported
    fstrim: /boot: the discard operation is not supported
     

    tower-diagnostics-20240701-1018.zip




    User Feedback

    Recommended Comments

    Go to Settings - Scheduler - TRIM and make a dummy change then hit apply, that will update to the new script, and you should not longer see those.

     

    The new script exists since v6.12 BTW, but with v6.12 fstrim did not try to TRIM the disks and flash drive, so it didn't cause the errors.

    • Thanks 1
    Link to comment

    I'm running 7.0.0-beta2 and I had this same thing. 

    I received this email report

     

    cron for user root /sbin/fstrim -a -v | logger &> /dev/null
    
    fstrim: /mnt/disk11: the discard operation is not supported
    fstrim: /mnt/disk10: the discard operation is not supported
    fstrim: /mnt/disk9: the discard operation is not supported
    fstrim: /mnt/disk8: the discard operation is not supported
    fstrim: /mnt/disk7: the discard operation is not supported
    fstrim: /mnt/disk6: the discard operation is not supported
    fstrim: /mnt/disk5: the discard operation is not supported
    fstrim: /mnt/disk4: the discard operation is not supported
    fstrim: /mnt/disk3: the discard operation is not supported
    fstrim: /mnt/disk2: the discard operation is not supported
    fstrim: /mnt/disk1: the discard operation is not supported
    fstrim: /boot: the discard operation is not supported

     

    I've applied the dummy change to see if this will resolve the error; but will this be reported for future releases (e.g rc1)?

    Link to comment
    2 hours ago, Jarsky said:

    but will this be reported for future releases (e.g rc1)?

    For anyone still using the old script, and that's from v6.11 BTW, the way to fix it to do the dummy change.

    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.

×
×
  • Create New...