Fs_mark is a benchmark designed to test your filesystem. It lets you test multible creations and writes of files across different directories and drives.
One way of running fs_mark looks like this:
./fs_mark -d testdir -s 1048576 -n 1024 -t 4 -v
-d lets you specify the directories you want to test-s size of the files-n number of files-t number of threads-v verbose outputRunning fs_mark like above will lead to a result like this one:
# ./fs_mark -d testdir -s 1048576 -n 1024 -t 4 -v
# Version 3.3, 4 thread(s) starting at Tue May 30 11:35:51 2017
# Sync method: INBAND FSYNC: fsync() per file in write loop.
# Directories: no subdirectories used
# File names: 40 bytes long, (16 initial bytes of time stamp with 24 random bytes at end of name)
# Files info: size 1048576 bytes, written with an IO size of 16384 bytes per write
# App overhead is time in microseconds spent in the test not doing file writing related system calls.
# All system call times are reported in microseconds.
FSUse% Count Size Files/sec App Overhead CREAT (Min/Avg/Max) WRITE (Min/Avg/Max) FSYNC (Min/Avg/Max) SYNC (Min/Avg/Max) CLOSE (Min/Avg/Max) UNLINK (Min/Avg/Max)
13 4096 1048576 42.8 170340 24 87 2141 17 27 2425 79384 91680 184577 0 0 0 2 6 1932 267 312 574