[LU-10410] Verify fstrim functionality on MDT

• Type: Improvement
• Resolution: Duplicate
• Priority: Minor
• Labels: ldiskfs
• Assignee: Saurabh Tandan (Inactive)
• Reporter: Andreas Dilger

Description

It would be useful to test the “fstrim” functionality with both MDT and OST devices, to ensure proper functionality and data correctness. My understanding is that fstrim is only supported for ldiskfs at this time, and needs to run with SSD storage.

In order to test this, verifiable data must be written into the filesystem, the filesystem mounted (concurrently) as type ldiskfs, fstrim run against the ldiskfs mount, then unmount and verify the data. For the MDT it would be useful to use DoM so that the MDT fills up with data more quickly.
 

Issue Links

• is related to: LU-11355 Add Lustre trim support
• is related to: LU-17722 wait_delete_completed() to trim underlying fs backed by tmpfs

Comments

[Andreas Dilger]

Usage of fstrim in test scripts added in patch https://review.whamcloud.com/54720 ("LU-17722 tests: trim tmpfs from wait_delete_completed()")

[Andreas Dilger]

We never did get a test out of LU-11355 so reopening this ticket to track adding an fstrim regression test.

[Andreas Dilger]

This should be put into a test script, rather than be done by hand, so that it can be run in the future, possibly as a regular part of autotest. It is possible to check if the underlying device is an SSD by checking /sys/block/<device>/queue/rotational is 0. The test would be skipped if this is 1.