1 .\" Copyright (c) 2000 Christoph Herrmann, Thomas-Henning von Kamptz
2 .\" Copyright (c) 1980, 1989, 1993 The Regents of the University of California.
3 .\" All rights reserved.
5 .\" This code is derived from software contributed to Berkeley by
6 .\" Christoph Herrmann and Thomas-Henning von Kamptz, Munich and Frankfurt.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgment:
18 .\" This product includes software developed by the University of
19 .\" California, Berkeley and its contributors, as well as Christoph
20 .\" Herrmann and Thomas-Henning von Kamptz.
21 .\" 4. Neither the name of the University nor the names of its contributors
22 .\" may be used to endorse or promote products derived from this software
23 .\" without specific prior written permission.
25 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
26 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
27 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
28 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
29 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
30 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
31 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
32 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
33 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
34 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
37 .\" $TSHeader: src/sbin/growfs/growfs.8,v 1.3 2000/12/12 19:31:00 tomsoft Exp $
45 .Nd grow size of an existing ufs file system
58 the disk must be labeled to a bigger size using
60 If you are using volumes you must enlarge them by using
63 extends the size of the file system on the specified special file.
66 can only enlarge unmounted file systems.
67 Do not try enlarging a mounted file system, your system may panic and you will
68 not be able to use the file system any longer.
71 options can not be changed by
73 In fact, you can only increase the size of the file system.
78 The following options are available:
79 .Bl -tag -width indent
82 Causes the new file system parameters to be printed out without actually
83 enlarging the file system.
88 will ask you if you took a backup of your data before and will do some tests
91 is currently mounted or whether there are any active snapshots on the file
93 This will be suppressed.
94 So use this option with great care!
98 of the file system after enlarging in sectors.
99 This value defaults to the size of the raw partition specified in
103 will enlarge the file system to the size of the entire partition).
106 .Dl growfs -s 4194304 /dev/vinum/testvol
109 .Pa /dev/vinum/testvol
110 up to 2GB if there is enough space in
111 .Pa /dev/vinum/testvol .
117 There may be cases on
121 does not recognize properly whether or not the file system is mounted and
122 exits with an error message.
126 if you are sure that the file system is not mounted.
127 It is also recommended to always use
129 after enlarging (just to be on the safe side).
131 For enlarging beyond certain limits, it is essential to have some free blocks
132 available in the first cylinder group.
133 If that space is not available in the first cylinder group, a critical data
134 structure has to be relocated into one of the new available cylinder groups.
137 3.x this will cause problems with
142 needs to be patched if you want to use
147 This patch is already integrated in
151 To avoid an unexpected relocation of that structure it is possible to use
154 on the first cylinder group to verify that
156 in the CYLINDER SUMMARY (internal cs) of the CYLINDER GROUP
159 As a rule of thumb for default file system parameters one block is needed for
160 every 2 GB of total file system size.
164 writes this critical structure to disk and reads it again later for doing more
166 This read operation will provide unexpected data when using
168 Therefore, this part can not really be simulated and will be skipped in test
179 .An Christoph Herrmann Aq chm@FreeBSD.org
180 .An Thomas-Henning von Kamptz Aq tomsoft@FreeBSD.org
181 .An The GROWFS team Aq growfs@Tomsoft.COM
185 command first appeared in