xref: /freebsd/sbin/newfs/newfs.8 (revision 3c4ba5f55438f7afd4f4b0b56f88f2bb505fd6a6)
1.\" Copyright (c) 1983, 1987, 1991, 1993, 1994
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)newfs.8	8.6 (Berkeley) 5/3/95
29.\" $FreeBSD$
30.\"
31.Dd October 21, 2022
32.Dt NEWFS 8
33.Os
34.Sh NAME
35.Nm newfs
36.Nd construct a new UFS1/UFS2 file system
37.Sh SYNOPSIS
38.Nm
39.Op Fl EJNUjlnt
40.Op Fl L Ar volname
41.Op Fl O Ar filesystem-type
42.Op Fl S Ar sector-size
43.Op Fl T Ar disktype
44.Op Fl a Ar maxcontig
45.Op Fl b Ar block-size
46.Op Fl c Ar blocks-per-cylinder-group
47.Op Fl d Ar max-extent-size
48.Op Fl e Ar maxbpg
49.Op Fl f Ar frag-size
50.Op Fl g Ar avgfilesize
51.Op Fl h Ar avgfpdir
52.Op Fl i Ar bytes
53.Op Fl k Ar held-for-metadata-blocks
54.Op Fl m Ar free-space
55.Op Fl o Ar optimization
56.Op Fl p Ar partition
57.Op Fl r Ar reserved
58.Op Fl s Ar size
59.Ar special
60.Sh DESCRIPTION
61The
62.Nm
63utility is used to initialize and clear file systems before first use.
64The
65.Nm
66utility builds a file system on the specified special file.
67(We often refer to the
68.Dq special file
69as the
70.Dq disk ,
71although the special file need not be a physical disk.
72In fact, it need not even be special.)
73Typically the defaults are reasonable, however
74.Nm
75has numerous options to allow the defaults to be selectively overridden.
76.Pp
77The following options define the general layout policies:
78.Bl -tag -width indent
79.It Fl E
80Erase the content of the disk before making the filesystem.
81The reserved area in front of the superblock (for bootcode) will not be erased.
82Erasing is only relevant to flash-memory or thinly provisioned devices.
83Erasing may take a long time.
84If the device does not support BIO_DELETE, the command will fail.
85.It Fl J
86Enable journaling on the new file system via gjournal.
87See
88.Xr gjournal 8
89for details.
90.It Fl L Ar volname
91Add a volume label to the new file system.
92Legal characters are alphanumerics, dashes, and underscores.
93.It Fl N
94Cause the file system parameters to be printed out
95without really creating the file system.
96.It Fl O Ar filesystem-type
97Use 1 to specify that a UFS1 format file system be built;
98use 2 to specify that a UFS2 format file system be built.
99The default format is UFS2.
100.It Fl T Ar disktype
101For backward compatibility.
102.It Fl U
103Enable soft updates on the new file system.
104.It Fl a Ar maxcontig
105Specify the maximum number of contiguous blocks that will be
106laid out before forcing a rotational delay.
107The default value is 16.
108See
109.Xr tunefs 8
110for more details on how to set this option.
111.It Fl b Ar block-size
112The block size of the file system, in bytes.
113It must be a power of 2.
114.\" If changing the default block size and it causes the default
115.\" fragment size to change, be sure to update the location of
116.\" the first backup superblock on the fsck_ffs.8 manual page.
117The
118default size is 32768 bytes, and the smallest allowable size is 4096 bytes.
119The optimal block:fragment ratio is 8:1.
120Other ratios are possible, but are not recommended,
121and may produce poor results.
122.It Fl c Ar blocks-per-cylinder-group
123The number of blocks per cylinder group in a file system.
124The default is to compute the maximum allowed by the other parameters.
125This value is
126dependent on a number of other parameters, in particular the block size
127and the number of bytes per inode.
128.It Fl d Ar max-extent-size
129The file system may choose to store large files using extents.
130This parameter specifies the largest extent size that may be used.
131The default value is the file system blocksize.
132It is presently limited to a maximum value of 16 times the
133file system blocksize and a minimum value of the file system blocksize.
134.It Fl e Ar maxbpg
135Indicate the maximum number of blocks any single file can
136allocate out of a cylinder group before it is forced to begin
137allocating blocks from another cylinder group.
138The default is about one quarter of the total blocks in a cylinder group.
139See
140.Xr tunefs 8
141for more details on how to set this option.
142.It Fl f Ar frag-size
143The fragment size of the file system in bytes.
144It must be a power of two
145ranging in value between
146.Ar blocksize Ns /8
147and
148.Ar blocksize .
149.\" If changing the default fragment size or it changes because of a
150.\" change to the default block size, be sure to update the location
151.\" of the first backup superblock on the fsck_ffs.8 manual page.
152The default is 4096 bytes.
153.It Fl g Ar avgfilesize
154The expected average file size for the file system.
155.It Fl h Ar avgfpdir
156The expected average number of files per directory on the file system.
157.It Fl i Ar bytes
158Specify the density of inodes in the file system.
159The default is to create an inode for every
160.Pq 2 * Ar frag-size
161bytes of data space.
162If fewer inodes are desired, a larger number should be used;
163to create more inodes a smaller number should be given.
164One inode is required for each distinct file, so this value effectively
165specifies the average file size on the file system.
166.It Fl j
167Enable soft updates journaling on the new file system.
168This flag is implemented by running the
169.Xr tunefs 8
170utility found in the user's
171.Dv $PATH .
172.Pp
173Enabling journaling reduces the time spent by
174.Xr fsck_ffs 8
175cleaning up a filesystem after a crash to a few seconds from minutes to hours.
176Without journaling, the time to recover after a crash is a function
177of the number of files in the filesystem and the size of the filesystem.
178With journaling, the time to recover after a crash is a function of the
179amount of activity in the filesystem in the minute before the crash.
180Journaled recovery time is usually only a few seconds and never
181exceeds a minute.
182.Pp
183The drawback to using journaling is that the writes to its log adds
184an extra write load to the media containing the filesystem.
185Thus a write-intensive workload will have reduced throughput on a
186filesystem running with journaling.
187.Pp
188Like all journaling filesystems, the journal recovery will only fix
189issues known to the journal.
190Specifically if a media error occurs,
191the journal will not know about it and hence will not fix it.
192Thus when using journaling, it is still necessary to run a full fsck
193every few months or after a filesystem panic to check for and fix
194any errors brought on by media failure.
195A full fsck can be done by running a background fsck on a live
196filesystem or by running with the
197.Fl f
198flag on an unmounted filesystem.
199When running
200.Xr fsck_ffs 8
201in background on a live filesystem the filesystem performance
202will be about half of normal during the time that the background
203.Xr fsck_ffs 8
204is running.
205Running a full fsck on a UFS filesystem is the equivalent of
206running a scrub on a ZFS filesystem.
207.Pp
208Presently it is not possible
209to run background fsck on filesystems enabled for journaling.
210.It Fl k Ar held-for-metadata-blocks
211Set the amount of space to be held for metadata blocks in each cylinder group.
212When set, the file system preference routines will try to save
213the specified amount of space immediately following the inode blocks
214in each cylinder group for use by metadata blocks.
215Clustering the metadata blocks speeds up random file access
216and decreases the running time of
217.Xr fsck 8 .
218By default
219.Nm
220sets it to half of the space reserved to minfree.
221.It Fl l
222Enable multilabel MAC on the new file system.
223.It Fl m Ar free-space
224The percentage of space reserved from normal users; the minimum free
225space threshold.
226The default value used is
227defined by
228.Dv MINFREE
229from
230.In ufs/ffs/fs.h ,
231currently 8%.
232See
233.Xr tunefs 8
234for more details on how to set this option.
235.It Fl n
236Do not create a
237.Pa .snap
238directory on the new file system.
239The resulting file system will not support snapshot generation, so
240.Xr dump 8
241in live mode and background
242.Xr fsck 8
243will not function properly.
244The traditional
245.Xr fsck 8
246and offline
247.Xr dump 8
248will work on the file system.
249This option is intended primarily for memory or vnode-backed file systems that
250do not require
251.Xr dump 8
252or
253.Xr fsck 8
254support.
255.It Fl o Ar optimization
256.Cm ( space
257or
258.Cm time ) .
259The file system can either be instructed to try to minimize the time spent
260allocating blocks, or to try to minimize the space fragmentation on the disk.
261If the value of minfree (see above) is less than 8%,
262the default is to optimize for
263.Cm space ;
264if the value of minfree is greater than or equal to 8%,
265the default is to optimize for
266.Cm time .
267See
268.Xr tunefs 8
269for more details on how to set this option.
270.It Fl p Ar partition
271The partition name (a..h) you want to use in case the underlying image
272is a file, so you do not have access to individual partitions through the
273filesystem.
274Can also be used with a device, e.g.,
275.Nm
276.Fl p Ar f
277.Ar /dev/da1s3
278is equivalent to
279.Nm
280.Ar /dev/da1s3f .
281.It Fl r Ar reserved
282The size, in sectors, of reserved space
283at the end of the partition specified in
284.Ar special .
285This space will not be occupied by the file system;
286it can be used by other consumers such as
287.Xr geom 4 .
288Defaults to 0.
289.It Fl s Ar size
290The size of the file system in sectors.
291This value defaults to the size of the
292raw partition specified in
293.Ar special
294less the
295.Ar reserved
296space at its end (see
297.Fl r ) .
298A
299.Ar size
300of 0 can also be used to choose the default value.
301A valid
302.Ar size
303value cannot be larger than the default one,
304which means that the file system cannot extend into the reserved space.
305.It Fl t
306Turn on the TRIM enable flag.
307If enabled, and if the underlying device supports the BIO_DELETE
308command, the file system will send a delete request to the underlying
309device for each freed block.
310The trim enable flag is typically set for flash-memory devices to
311reduce write amplification which reduces wear on write-limited
312flash-memory and often improves long-term performance.
313Thinly provisioned storage also benefits by returning unused blocks to
314the global pool.
315.El
316.Pp
317The following options override the standard sizes for the disk geometry.
318Their default values are taken from the disk label.
319Changing these defaults is useful only when using
320.Nm
321to build a file system whose raw image will eventually be used on a
322different type of disk than the one on which it is initially created
323(for example on a write-once disk).
324Note that changing any of these values from their defaults will make
325it impossible for
326.Xr fsck 8
327to find the alternate superblocks if the standard superblock is lost.
328.Bl -tag -width indent
329.It Fl S Ar sector-size
330The size of a sector in bytes (almost never anything but 512).
331.El
332.Sh NOTES ON THE NAMING
333.Dq newfs
334is a common name prefix for utilities creating filesystems, with the suffix
335indicating the type of the filesystem, for instance
336.Xr newfs_msdos 8 .
337The
338.Nm
339utility is a special case which predates that convention.
340.Sh EXAMPLES
341.Dl newfs /dev/ada3s1a
342.Pp
343Creates a new ufs file system on
344.Pa ada3s1a .
345The
346.Nm
347utility will use a block size of 32768 bytes, a fragment size of 4096 bytes
348and the largest possible number of blocks per cylinders group.
349These values tend to produce better performance for most applications
350than the historical defaults
351(8192 byte block size and 1024 byte fragment size).
352This large fragment size may lead to much wasted space
353on file systems that contain many small files.
354.Sh SEE ALSO
355.Xr fdformat 8 ,
356.Xr geom 4 ,
357.Xr disktab 5 ,
358.Xr fs 5 ,
359.Xr camcontrol 8 ,
360.Xr dump 8 ,
361.Xr dumpfs 8 ,
362.Xr fsck 8 ,
363.Xr gjournal 8 ,
364.Xr gpart 8 ,
365.Xr growfs 8 ,
366.Xr gvinum 8 ,
367.Xr makefs 8 ,
368.Xr mount 8 ,
369.Xr newfs_msdos 8 ,
370.Xr tunefs 8
371.Rs
372.%A M. McKusick
373.%A W. Joy
374.%A S. Leffler
375.%A R. Fabry
376.%T A Fast File System for UNIX
377.%J ACM Transactions on Computer Systems 2
378.%V 3
379.%P pp 181-197
380.%D August 1984
381.%O (reprinted in the BSD System Manager's Manual)
382.Re
383.Sh HISTORY
384The
385.Nm
386utility appeared in
387.Bx 4.2 .
388