Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1922857 - Fstrim is not working anymore for NTFS partition
Summary: Fstrim is not working anymore for NTFS partition
Keywords:
Status: CLOSED DUPLICATE of bug 1926954
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-31 23:07 UTC by Kurt Heine
Modified: 2021-02-09 21:34 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-09 21:34:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kurt Heine 2021-01-31 23:07:44 UTC 
1. Please describe the problem:
fstrim service fails

2. What is the Version-Release number of the kernel:

5.10.10-200.fc33.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

5.10.8-200.fc33.x86_64? but may not have


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

restart system

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:

No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Comment 1 Kurt Heine 2021-01-31 23:08:09 UTC 
service log

February 1, 2021
9:46 AM
fstrim.service: Consumed 3.657s CPU time.
systemd
9:46 AM
Failed to start Discard unused blocks on filesystems from /etc/fstab.
systemd
9:46 AM
fstrim.service: Failed with result 'exit-code'.
systemd
9:46 AM
fstrim.service: Main process exited, code=exited, status=64/USAGE
systemd
9:46 AM
/: 130.9 GiB (140536975360 bytes) trimmed on /dev/nvme1n1p4
fstrim
9:46 AM
/boot: 0 B (0 bytes) trimmed on /dev/nvme1n1p1
fstrim
9:46 AM
/boot/efi: 578.5 MiB (606601216 bytes) trimmed on /dev/nvme1n1p2
fstrim
9:45 AM
fstrim: /mnt/windows: FITRIM ioctl failed: Device or resource busy
fstrim
9:45 AM
Starting Discard unused blocks on filesystems from /etc/fstab...
systemd
9:42 AM
fstrim.service: Consumed 3.688s CPU time.
Comment 2 Kurt Heine 2021-01-31 23:08:35 UTC 
Reported on ArchLinux

https://bbs.archlinux.org/viewtopic.php?id=262243
Comment 3 Richard W.M. Jones 2021-02-09 21:34:17 UTC 

*** This bug has been marked as a duplicate of bug 1926954 ***
Note You need to log in before you can comment on or make changes to this bug.