Lines Matching +full:a +full:- +full:8

18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
33 .Nd construct a new UFS1/UFS2 file system
38 .Op Fl O Ar filesystem-type
39 .Op Fl S Ar sector-size
41 .Op Fl a Ar maxcontig
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
63 utility builds a file system on the specified special file.
68 although the special file need not be a physical disk.
75 .Bl -tag -width indent
79 Erasing is only relevant to flash-memory or thinly provisioned devices.
80 Erasing may take a long time.
85 .Xr gjournal 8
88 Add a volume label to the new file system.
93 .It Fl O Ar filesystem-type
94 Use 1 to specify that a UFS1 format file system be built;
95 use 2 to specify that a UFS2 format file system be built.
103 .Xr tunefs 8
105 .It Fl a Ar maxcontig
107 laid out before forcing a rotational delay.
110 .Xr tunefs 8
112 .It Fl b Ar block-size
114 It must be a power of 2.
117 .\" the first backup superblock on the fsck_ffs.8 manual page.
120 The optimal block:fragment ratio is 8:1.
123 .It Fl c Ar blocks-per-cylinder-group
124 The number of blocks per cylinder group in a file system.
127 dependent on a number of other parameters, in particular the block size
129 .It Fl d Ar max-extent-size
133 It is presently limited to a maximum value of 16 times the
134 file system blocksize and a minimum value of the file system blocksize.
137 allocate out of a cylinder group before it is forced to begin
139 The default is about one quarter of the total blocks in a cylinder group.
141 .Xr tunefs 8
143 .It Fl f Ar frag-size
145 It must be a power of two
147 .Ar blocksize Ns /8
150 .\" If changing the default fragment size or it changes because of a
152 .\" of the first backup superblock on the fsck_ffs.8 manual page.
161 .Pq 2 * Ar frag-size
163 If fewer inodes are desired, a larger number should be used;
164 to create more inodes a smaller number should be given.
170 .Xr tunefs 8
175 .Xr fsck_ffs 8
176 cleaning up a filesystem after a crash to a few seconds from minutes to hours.
177 Without journaling, the time to recover after a crash is a function
179 With journaling, the time to recover after a crash is a function of the
181 Journaled recovery time is usually only a few seconds and never
182 exceeds a minute.
186 Thus a write-intensive workload will have reduced throughput on a
191 Specifically if a media error occurs,
193 Thus when using journaling, it is still necessary to run a full fsck
194 every few months or after a filesystem panic to check for and fix
196 A full fsck can be done by running a background fsck on a live
201 .Xr fsck_ffs 8
202 in background on a live filesystem the filesystem performance
204 .Xr fsck_ffs 8
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
215 .Xr fsck 8 .
221 .It Fl m Ar free-space
229 currently 8%.
231 .Xr tunefs 8
234 Do not create a
238 .Xr dump 8
240 .Xr fsck 8
243 .Xr fsck 8
245 .Xr dump 8
247 This option is intended primarily for memory or vnode-backed file systems that
249 .Xr dump 8
251 .Xr fsck 8
259 If the value of minfree (see above) is less than 8%,
262 if the value of minfree is greater than or equal to 8%,
266 .Xr tunefs 8
269 The partition name (a..h) you want to use in case the underlying image
270 is a file, so you do not have access to individual partitions through the
272 Can also be used with a device, e.g.,
296 A
299 A valid
306 command, the file system will send a delete request to the underlying
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.
319 to build a file system whose raw image will eventually be used on a
321 (for example on a write-once disk).
324 .Xr fsck 8
326 .Bl -tag -width indent
327 .It Fl S Ar sector-size
328 The size of a sector in bytes (almost never anything but 512).
332 is a common name prefix for utilities creating filesystems, with the suffix
334 .Xr newfs_msdos 8 .
337 utility is a special case which predates that convention.
341 Creates a new ufs file system on
345 utility will use a block size of 32768 bytes, a fragment size of 4096 bytes
357 .Xr camcontrol 8 ,
358 .Xr dump 8 ,
359 .Xr dumpfs 8 ,
360 .Xr fdformat 8 ,
361 .Xr fsck 8 ,
362 .Xr gjournal 8 ,
363 .Xr gpart 8 ,
364 .Xr growfs 8 ,
365 .Xr makefs 8 ,
366 .Xr mount 8 ,
367 .Xr newfs_msdos 8 ,
368 .Xr tunefs 8
370 .%A M. McKusick
371 .%A W. Joy
372 .%A S. Leffler
373 .%A R. Fabry
374 .%T A Fast File System for UNIX
377 .%P pp 181-197