2
.TH FSTRIM 8 "Nov 2010"
4
fstrim \- discard unused blocks on a mounted filesystem
18
is used on a mounted filesystem to discard (or "trim") blocks which are not in
19
use by the filesystem. This is useful for solid-state drives (SSDs) and
20
thinly-provisioned storage.
24
will discard all unused blocks in the filesystem. Options may be used to
25
modify this behavior based on range or size, as explained below.
29
argument is the pathname of the directory where the filesystem
33
The \fIoffset\fR, \fIlength\fR, and \fIminimum-free-extent\fR arguments may be
34
followed by binary (2^N) suffixes KiB, MiB, GiB, TiB, PiB and EiB (the "iB" is
35
optional, e.g. "K" has the same meaning as "KiB") or decimal (10^N) suffixes
36
KB, MB, GB, PB and EB.
37
.IP "\fB\-h, \-\-help\fP"
39
.IP "\fB\-o, \-\-offset\fP \fIoffset\fP"
40
Byte offset in filesystem from which to begin searching for free blocks
41
to discard. Default value is zero, starting at the beginning of the
43
.IP "\fB\-l, \-\-length\fP \fIlength\fP"
44
Number of bytes after starting point to search for free blocks to discard.
45
If the specified value extends past the end of the filesystem,
47
will stop at the filesystem size boundary. Default value extends to the end
49
.IP "\fB\-m, \-\-minimum\fP \fIminimum-free-extent\fP"
50
Minimum contiguous free range to discard, in bytes. (This value is internally
51
rounded up to a multiple of the filesystem block size). Free ranges smaller
52
than this will be ignored. By increasing this value, the fstrim operation
53
will complete more quickly for filesystems with badly fragmented freespace,
54
although not all blocks will be discarded. Default value is zero, discard
56
.IP "\fB\-v, \-\-verbose\fP"
57
Verbose execution. When specified
59
will output the number of bytes passed from the filesystem
60
down the block stack to the device for potential discard. This number is a
61
maximum discard amount from the storage device's perspective, because
63
ioctl called repeated will keep sending the same sectors for discard repeatedly.
66
will report the same potential discard bytes each time, but only sectors which
67
had been written to between the discards would actually be discarded by the
68
storage device. Further, the kernel block layer reserves the right to adjust
69
the discard ranges to fit raid stripe geometry, non-trim capable devices in a
70
LVM setup, etc. These reductions would not be reflected in fstrim_range.len
77
Lukas Czerner <lczerner@redhat.com>
78
Karel Zak <kzak@redhat.com>
83
The fstrim command is part of the util-linux package and is available from
84
ftp://ftp.kernel.org/pub/linux/utils/util-linux/.