Bug 1922857

Summary: Fstrim is not working anymore for NTFS partition
Product: [Fedora] Fedora Reporter: Kurt Heine <kheine7>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 33CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, itamar, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, rjones, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-09 21:34:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***