fstrim fails on some drives with "the discard operation is not supported"
Bug #1976121 reported by
Jeff Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Checkbox Provider - Base |
Expired
|
Undecided
|
Unassigned | ||
| Checkbox Provider - Resource |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
sometimes fstrim fails with this message:
fstrim: /: the discard operation is not supported
This seems to provide some clue:
https:/
+++++
Specifically this comment:
Is trim actually supported by your SSD ? Type
sudo hdparm -I /dev/sda | grep TRIM
(assuming sda is your drive).
Is there a line saying that TRIM is supported ?
+++++
We need to see if we can reproduce this on NVMe and SSDs in the lab, but I suspect we should really have some update to the block_device_
block_device_
and then only run the fstrim test if the drive says it supports trim.
| summary: |
- fstrim fails when not supported + fstrim fails on some drives with "the discard operation is not + supported" |
| affects: | plainbox-provider-certification-server → plainbox-provider-checkbox |
| tags: | added: servcert-381 |
Revision history for this message
| Maksim Beliaev (beliaev-maksim) wrote | #1 |
| Changed in plainbox-provider-checkbox: | |
| status: | New → Expired |
Revision history for this message
| Maksim Beliaev (beliaev-maksim) wrote | #2 |
| Changed in plainbox-provider-resource: | |
| status: | New → Expired |
To post a comment you must log in.
Bug was migrated to GitHub: https:/
Bug is no more monitored here.