xref: /freebsd/sbin/newfs/newfs.8 (revision a3cf0ef5a295c885c895fabfd56470c0d1db322d)
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.\" 4. 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 September 14, 2010
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 EJNUln
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 m Ar free-space
54.Op Fl o Ar optimization
55.Op Fl p Ar partition
56.Op Fl r Ar reserved
57.Op Fl s Ar size
58.Ar special
59.Sh DESCRIPTION
60The
61.Nm
62utility is used to initialize and clear file systems before first use.
63The
64.Nm
65utility builds a file system on the specified special file.
66(We often refer to the
67.Dq special file
68as the
69.Dq disk ,
70although the special file need not be a physical disk.
71In fact, it need not even be special.)
72Typically the defaults are reasonable, however
73.Nm
74has numerous options to allow the defaults to be selectively overridden.
75.Pp
76The following options define the general layout policies:
77.Bl -tag -width indent
78.It Fl E
79Erase the content of the disk before making the filesystem.
80The reserved area in front of the superblock (for bootcode) will not be erased.
81.Pp
82This option is only relevant for flash based storage devices that use
83wear-leveling algorithms.
84.Pp
85Erasing may take a long time as it writes to every sector on the disk.
86.It Fl J
87Enable journaling on the new file system via gjournal.
88See
89.Xr gjournal 8
90for details.
91.It Fl L Ar volname
92Add a volume label to the new file system.
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.
114The
115default size is 16384 bytes, and the smallest allowable size is 4096 bytes.
116The optimal block:fragment ratio is 8:1.
117Other ratios are possible, but are not recommended,
118and may produce poor results.
119.It Fl c Ar blocks-per-cylinder-group
120The number of blocks per cylinder group in a file system.
121The default is to compute the maximum allowed by the other parameters.
122This value is
123dependent on a number of other parameters, in particular the block size
124and the number of bytes per inode.
125.It Fl d Ar max-extent-size
126The file system may choose to store large files using extents.
127This parameter specifies the largest extent size that may be used.
128The default value is the file system blocksize.
129It is presently limited to a maximum value of 16 times the
130file system blocksize and a minimum value of the file system blocksize.
131.It Fl e Ar maxbpg
132Indicate the maximum number of blocks any single file can
133allocate out of a cylinder group before it is forced to begin
134allocating blocks from another cylinder group.
135The default is about one quarter of the total blocks in a cylinder group.
136See
137.Xr tunefs 8
138for more details on how to set this option.
139.It Fl f Ar frag-size
140The fragment size of the file system in bytes.
141It must be a power of two
142ranging in value between
143.Ar blocksize Ns /8
144and
145.Ar blocksize .
146The default is 2048 bytes.
147.It Fl g Ar avgfilesize
148The expected average file size for the file system.
149.It Fl h Ar avgfpdir
150The expected average number of files per directory on the file system.
151.It Fl i Ar bytes
152Specify the density of inodes in the file system.
153The default is to create an inode for every
154.Pq 4 * Ar frag-size
155bytes of data space.
156If fewer inodes are desired, a larger number should be used;
157to create more inodes a smaller number should be given.
158One inode is required for each distinct file, so this value effectively
159specifies the average file size on the file system.
160.It Fl l
161Enable multilabel MAC on the new file system.
162.It Fl m Ar free-space
163The percentage of space reserved from normal users; the minimum free
164space threshold.
165The default value used is
166defined by
167.Dv MINFREE
168from
169.In ufs/ffs/fs.h ,
170currently 8%.
171See
172.Xr tunefs 8
173for more details on how to set this option.
174.It Fl n
175Do not create a
176.Pa .snap
177directory on the new file system.
178The resulting file system will not support snapshot generation, so
179.Xr dump 8
180in live mode and background
181.Xr fsck 8
182will not function properly.
183The traditional
184.Xr fsck 8
185and offline
186.Xr dump 8
187will work on the file system.
188This option is intended primarily for memory or vnode-backed file systems that
189do not require
190.Xr dump 8
191or
192.Xr fsck 8
193support.
194.It Fl o Ar optimization
195.Cm ( space
196or
197.Cm time ) .
198The file system can either be instructed to try to minimize the time spent
199allocating blocks, or to try to minimize the space fragmentation on the disk.
200If the value of minfree (see above) is less than 8%,
201the default is to optimize for
202.Cm space ;
203if the value of minfree is greater than or equal to 8%,
204the default is to optimize for
205.Cm time .
206See
207.Xr tunefs 8
208for more details on how to set this option.
209.It Fl p Ar partition
210The partition name (a..h) you want to use in case the underlying image
211is a file, so you don't have access to individual partitions through the
212filesystem.
213Can also be used with a device, e.g.
214.Nm
215.Fl p Ar f
216.Ar /dev/da1s3
217is equivalent to
218.Nm
219.Ar /dev/da1s3f .
220.It Fl r Ar reserved
221The size, in sectors, of reserved space
222at the end of the partition specified in
223.Ar special .
224This space will not be occupied by the file system;
225it can be used by other consumers such as
226.Xr geom 4 .
227Defaults to 0.
228.It Fl s Ar size
229The size of the file system in sectors.
230This value defaults to the size of the
231raw partition specified in
232.Ar special
233less the
234.Ar reserved
235space at its end (see
236.Fl r ) .
237A
238.Ar size
239of 0 can also be used to choose the default value.
240A valid
241.Ar size
242value cannot be larger than the default one,
243which means that the file system cannot extend into the reserved space.
244.El
245.Pp
246The following options override the standard sizes for the disk geometry.
247Their default values are taken from the disk label.
248Changing these defaults is useful only when using
249.Nm
250to build a file system whose raw image will eventually be used on a
251different type of disk than the one on which it is initially created
252(for example on a write-once disk).
253Note that changing any of these values from their defaults will make
254it impossible for
255.Xr fsck 8
256to find the alternate superblocks if the standard superblock is lost.
257.Bl -tag -width indent
258.It Fl S Ar sector-size
259The size of a sector in bytes (almost never anything but 512).
260.El
261.Sh EXAMPLES
262.Dl newfs /dev/ad3s1a
263.Pp
264Creates a new ufs file system on
265.Pa ad3s1a .
266The
267.Nm
268utility will use a block size of 16384 bytes, a fragment size of 2048 bytes
269and the largest possible number of blocks per cylinders group.
270These values tend to produce better performance for most applications
271than the historical defaults
272(8192 byte block size and 1024 byte fragment size).
273This large fragment size may lead to much wasted space
274on file systems that contain many small files.
275.Sh SEE ALSO
276.Xr fdformat 1 ,
277.Xr geom 4 ,
278.Xr disktab 5 ,
279.Xr fs 5 ,
280.Xr bsdlabel 8 ,
281.Xr camcontrol 8 ,
282.Xr dump 8 ,
283.Xr dumpfs 8 ,
284.Xr fsck 8 ,
285.Xr gjournal 8 ,
286.Xr mount 8 ,
287.Xr tunefs 8 ,
288.Xr gvinum 8
289.Rs
290.%A M. McKusick
291.%A W. Joy
292.%A S. Leffler
293.%A R. Fabry
294.%T A Fast File System for UNIX
295.%J ACM Transactions on Computer Systems 2
296.%V 3
297.%P pp 181-197
298.%D August 1984
299.%O (reprinted in the BSD System Manager's Manual)
300.Re
301.Sh HISTORY
302The
303.Nm
304utility appeared in
305.Bx 4.2 .
306