1
2xfs_growfs(8)               System Manager's Manual              xfs_growfs(8)
3
4
5

NAME

7       xfs_growfs, xfs_info - expand an XFS filesystem
8

SYNOPSIS

10       xfs_growfs  [  -dilnrx  ] [ -D size ] [ -e rtextsize ] [ -L size ] [ -m
11       maxpct ] [ -t mtab ] [ -R size ] mount-point
12       xfs_growfs -V
13
14       xfs_info [ -t mtab ] mount-point
15       xfs_info -V
16

DESCRIPTION

18       xfs_growfs expands an existing XFS filesystem (see xfs(5)).  The mount-
19       point argument is the pathname of the directory where the filesystem is
20       mounted. The filesystem must be mounted to  be  grown  (see  mount(8)).
21       The  existing contents of the filesystem are undisturbed, and the added
22       space becomes available for additional file storage.
23
24       xfs_info is equivalent to invoking xfs_growfs with the -n  option  (see
25       discussion below).
26

OPTIONS

28       -d | -D size
29              Specifies  that  the  data  section  of the filesystem should be
30              grown. If the -D size option is given, the data section is grown
31              to that size, otherwise the data section is grown to the largest
32              size possible with the -d  option.  The  size  is  expressed  in
33              filesystem blocks.
34
35       -e     Allows the real-time extent size to be specified. In mkfs.xfs(8)
36              this is specified with -r extsize=nnnn.
37
38       -i     The new log is  an  internal  log  (inside  the  data  section).
39              [NOTE: This option is not implemented]
40
41       -l | -L size
42              Specifies  that  the  log  section  of  the filesystem should be
43              grown, shrunk, or moved. If the -L size option is given, the log
44              section  is  changed  to  be that size, if possible. The size is
45              expressed in filesystem blocks.  The size  of  an  internal  log
46              must be smaller than the size of an allocation group (this value
47              is printed at mkfs(8) time). If neither -i nor -x is given  with
48              -l,  the  log  continues  to  be  internal or external as it was
49              before.  [NOTE: These options are not implemented]
50
51       -m     Specify a new value for the maximum percentage of space  in  the
52              filesystem  that can be allocated as inodes. In mkfs.xfs(8) this
53              is specified with -i maxpct=nn.
54
55       -n     Specifies that no change to the filesystem is to be  made.   The
56              filesystem  geometry  is  printed, and argument checking is per‐
57              formed, but no growth occurs.  See output examples below.
58
59       -r | -R size
60              Specifies that the real-time section of the filesystem should be
61              grown.  If the -R size option is given, the real-time section is
62              grown to that size, otherwise the real-time section is grown  to
63              the  largest  size  possible  with  the  -r  option. The size is
64              expressed in filesystem blocks.  The filesystem does not need to
65              have  contained a real-time section before the xfs_growfs opera‐
66              tion.
67
68       -t     Specifies an alternate mount table file (default is /proc/mounts
69              if  it  exists, else /etc/mtab).  This is used when working with
70              filesystems mounted without writing to /etc/mtab file - refer to
71              mount(8) for further details.
72
73       -V     Prints the version number and exits. The mount-point argument is
74              not required with -V.
75
76       xfs_growfs is most often used in conjunction with logical volumes  (see
77       md(4)  and lvm(8) on Linux).  However, it can also be used on a regular
78       disk partition, for example if a  partition  has  been  enlarged  while
79       retaining the same starting block.
80

PRACTICAL USE

82       Filesystems  normally  occupy all of the space on the device where they
83       reside. In order to grow a filesystem, it is necessary to provide added
84       space  for it to occupy. Therefore there must be at least one spare new
85       disk partition available. Adding the space is often  done  through  the
86       use of a logical volume manager.
87

EXAMPLES

89       Understanding xfs_info output.
90
91       Suppose one has the following "xfs_info /dev/sda" output:
92
93         meta-data=/dev/sda      isize=256    agcount=32, agsize=16777184 blks
94                  =              sectsz=512   attr=2
95         data     =              bsize=4096   blocks=536869888, imaxpct=5
96                  =              sunit=32     swidth=128 blks
97         naming   =version 2     bsize=4096
98         log      =internal      bsize=4096   blocks=32768, version=2
99                  =              sectsz=512   sunit=32 blks, lazy-count=1
100         realtime =none          extsz=524288 blocks=0, rtextents=0
101
102       Here,  the  data  section of the output indicates "bsize=4096", meaning
103       the data block size for this filesystem is 4096  bytes.   This  section
104       also  shows  "sunit=32 swidth=128 blks", which means the stripe unit is
105       32*4096 bytes = 128 kibibytes and the stripe width is 128*4096 bytes  =
106       512  kibibytes.   A single stripe of this filesystem therefore consists
107       of four stripe units (128 blocks / 32 blocks per unit).
108

SEE ALSO

110       mkfs.xfs(8), md(4), lvm(8), mount(8).
111
112
113
114                                                                 xfs_growfs(8)
Impressum