growfs(1M)
NAME
growfs - non-destructively expand a UFS file system
SYNOPSIS
/usr/sbin/growfs [-M mount-point] [newfs-options] [raw-
device]
DESCRIPTION
growfs non-destructively expands a mounted or unmounted UNIX
file system (UFS) to the size of the file system's slice(s).
Typically, disk space is expanded by first adding a slice to
a metadevice, then running the growfs command. When adding
space to a mirror, you expand each submirror before expand-
ing the file system. On a trans metadevice, the master dev-
ice is expanded, not the trans metadevice. Then the growfs
command is run on the trans metadevice. (You can add space
to a logging device, but you do not need to run the growfs
command. The new space is automatically recognized.)
growfs will ``write-lock'' (see lockfs(1M)) a mounted file
system when expanding. The length of time the file system is
write-locked can be shortened by expanding the file system
in stages. For instance, to expand a 1 Gbyte file system to
2 Gbytes, the file system can be grown in 16 Mbyte stages
using the -s option to specify the total size of the new
file system at each stage. The argument for -s is the
number of sectors, and must be a multiple of the cylinder
size. Note: The file system cannot be grown if a cylinder
size of less than 2 is specified. Refer to the newfs(1M) man
page for information on the options available when growing a
file system.
growfs displays the same information as mkfs during the
expansion of the file system.
If growfs is aborted, recover any lost free space by
unmounting the file system and running the fsck command, or
run the growfs command again.
OPTIONS
Root privileges are required for all of the following
options.
-M mount-point
The file system to be expanded is mounted on mount-
point. File system locking (lockfs) will be used.
newfs-options
The options are documented in the newfs man page.
raw-device
Specifies the name of a raw metadevice or raw special
device, residing in /dev/md/rdsk, or /dev/rdsk,
respectively, including the disk slice, where you want
the file system to be grown.
EXAMPLES
Example 1: Expanding nonmetadevice slice for /export file
system
The following example expands a nonmetadevice slice for the
/export file system. In this example, the existing slice,
/dev/dsk/c1t0d0s3, is converted to a metadevice so addi-
tional slices can be concatenated.
# metainit -f d8 2 1 c1t0d0s3 1 c2t0d0s3
# umount /export
Example 2: Associate /export with new metadevice
Edit the /etc/vfstab file to change the entry for /export to
the newly defined metadevice, d8.
# mount /export
# growfs -M /export /dev/md/rdsk/d8
The first example starts by running the metainit command
with the -f option to force the creation of a new con-
catenated metadevice d8, which consists of the existing
slice /dev/dsk/c1t0d0s3 and a new slice /dev/dsk/c2t0d0s3.
Next, the file system on /export must be unmounted. The
/etc/vfstab file is edited to change the entry for /export
to the newly defined metadevice name, rather than the slice
name. After the file system is remounted, the growfs command
is run to expand the file system. The file system will span
the entire metadevice when growfs completes. The -M option
enables the growfs command to expand a mounted file system.
During the expansion, write access for /export is suspended
until growfs unlocks the file system. Read access is not
affected, though access times are not kept when the lock is
in effect.
Example 3: Dynamic Expansion of /export file system
The following example picks up from the previous one. Here,
the /export file system mounted on metadevice d8 is dynami-
cally expanded.
# metattach d8 c0t1d0s2
# growfs -M /export /dev/md/rdsk/d8
This example begins by using the metattach command to dynam-
ically concatenate a new slice, /dev/dsk/c0t1d0s2, to the
end of an existing metadevice, d8. Next, the growfs command
specifies that the mount-point is /export and that it is to
be expanded onto the raw metadevice /dev/md/rdsk/d8. The
file system will span the entire metadevice when growfs com-
pletes. During the expansion, write access for /export is
suspended until growfs unlocks the file system. Read access
is not affected, though access times are not kept when the
lock is in effect.
Example 4: Expanding mounted file system to existing mirror
The following example expands a mounted file system /files,
to an existing mirror, d80, which contains two submirrors,
d9 and d10.
# metattach d9 c0t2d0s5
# metattach d10 c0t3d0s5
# growfs -M /files /dev/md/rdsk/d80
In this example, the metattach command dynamically con-
catenates the new slices to each submirror. The metattach
command must be run for each submirror. The mirror will
automatically grow when the last submirror is dynamically
concatenated. The mirror will grow to the size of the smal-
lest submirror. The growfs command then expands the file
system. The growfs command specifies that the mount-point
is /files and that it is to be expanded onto the raw meta-
device /dev/md/rdsk/d80. The file system will span the
entire mirror when the growfs command completes. During the
expansion, write access for the file system is suspended
until growfs unlocks the file system. Read access is not
affected, though access times are not kept when the lock is
in effect.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWmdu |
|_____________________________|_____________________________|
SEE ALSO
fsck(1M), lockfs(1M), mkfs(1M), metattach(1M), newfs(1M),
attributes(5)
Solaris Volume Manager Administration Guide
LIMITATIONS
Only UFS file systems (either mounted or unmounted) can be
expanded using the growfs command. Once a file system is
expanded, it cannot be decreased in size. The following con-
ditions prevent you from expanding file systems: When acct
is activated and the accounting file is on the target dev-
ice. When C2 security is activated and the logging file is
on the target file system. When there is a local swap file
in the target file system. When the file system is root (/),
/usr, or swap.
Man(1) output converted with
man2html