[LU-19219] Change in ("fstrim -v") with EXT4_BG_TRIMMED

• Type: Bug
• Resolution: Unresolved
• Priority: Medium
• Severity: 3
• Assignee: Shaun Tancheff
• Reporter: Shaun Tancheff

Description

With Lustre version 2.15.4.1_cray_12_gc624701-46 successive fstrim commands act only on blocks that have been deleted since the last trim:

[root@kjlmo1n02 ~]# fstrim -v /data/kjlmo1n03:md65
/data/kjlmo1n03:md65: 5.5 TiB (6101931544576 bytes) trimmed
[root@kjlmo1n02 ~]# fstrim -v /data/kjlmo1n03:md65
/data/kjlmo1n03:md65: 0 B (0 bytes) trimmed
[root@kjlmo1n02 ~]#

In Lustre 2.15.4.2_cray_237_g3b03a62-243, however, this behavior has changed so that all blocks are trimmed every time:

[root@e2kd1n002 ~]# fstrim -v /data/e2kd1n003:md65
/data/e2kd1n003:md65: 22.1 TiB (24245231648768 bytes) trimmed
[root@e2kd1n002 ~]# fstrim -v /data/e2kd1n003:md65
/data/e2kd1n003:md65: 22.1 TiB (24245231648768 bytes) trimmed
[root@e2kd1n002 ~]#

Issue Links

• is related to: LU-14712 make TRIM state persistent across reboots