Lines Matching +full:free +full:- +full:running
38 .Op Fl O Ar filesystem-type
39 .Op Fl S Ar sector-size
42 .Op Fl b Ar block-size
43 .Op Fl c Ar blocks-per-cylinder-group
44 .Op Fl d Ar max-extent-size
46 .Op Fl f Ar frag-size
50 .Op Fl k Ar held-for-metadata-blocks
51 .Op Fl m Ar free-space
75 .Bl -tag -width indent
79 Erasing is only relevant to flash-memory or thinly provisioned devices.
93 .It Fl O Ar filesystem-type
112 .It Fl b Ar block-size
123 .It Fl c Ar blocks-per-cylinder-group
129 .It Fl d Ar max-extent-size
143 .It Fl f Ar frag-size
161 .Pq 2 * Ar frag-size
169 This flag is implemented by running the
186 Thus a write-intensive workload will have reduced throughput on a
187 filesystem running with journaling.
196 A full fsck can be done by running a background fsck on a live
197 filesystem or by running with the
200 When running
205 is running.
206 Running a full fsck on a UFS filesystem is the equivalent of
207 running a scrub on a ZFS filesystem.
208 .It Fl k Ar held-for-metadata-blocks
214 and decreases the running time of
221 .It Fl m Ar free-space
222 The percentage of space reserved from normal users; the minimum free
247 This option is intended primarily for memory or vnode-backed file systems that
308 The trim enable flag is typically set for flash-memory devices to
309 reduce write amplification which reduces wear on write-limited
310 flash-memory and often improves long-term performance.
321 (for example on a write-once disk).
326 .Bl -tag -width indent
327 .It Fl S Ar sector-size
377 .%P pp 181-197