logo

Manual Pages

Table of Contents

NAME

na_df - display free disk space

SYNOPSIS

df [ -i | -r ] [ -h | -k | -m | -g | -t ] [ pathname ]

DESCRIPTION

df displays statistics about the amount of free disk space in one or all volumes on the filer. All sizes are reported in 1024-byte blocks, unless otherwise requested by one of the -h, -k, -m, -g, or -t options.

The pathname parameter is the path name to a volume. If it is specified, df reports only on the corresponding volume; otherwise, it reports on every on-line volume.

For each volume, df displays statistics about snapshots on a separate line from statistics about the active file system. The snapshot line reports the amount of space consumed by all the snapshots in the system. Blocks that are referenced by both the active file system and by one or more snapshots are counted only in the active file system line, not in the snapshot line.

If snapshots consume more space than has been reserved for them by the snap reserve command (see na_snap(1)), then the excess space consumed by snapshots is reported as used by the active file system as well as by snapshots. In this case, it may appear that more blocks have been used in total than are actually present in the file system.

With the -r option, df displays the amount of reserved space in the volume. The reserved space is already counted in the used space, so the -r option can be used to see what portion of the used space represents space reserved for future use.

The -h option scales the units of each size related field to be KB, MB, GB, or TB, whichever is most appropriate for the value being displayed. The -k, -m, -g, and -t options scale each size related field of the output to be expressed in kilobytes, megabytes, gigabytes, or terabytes respectively. Unit values are based on powers of two, so, for example, one megabyte is equal to 1,048,576 bytes.

With the -i option, df displays statistics on the number of free inodes.

EXAMPLES

The following example shows file system disk space usage: 
  toaster> df
  Filesystem          kbytes   used     avail   capacity Mounted on
  /vol/vol0           4339168  1777824  2561344 41%      /vol/vol0
  /vol/vol0/.snapshot 1084788  956716   128072  88%      /vol/vol0/.snapshot

If snapshots consume more than 100% of the space reserved for them, then either the snapshot reserve should be increased (using snap reserve ) or else some of the snapshots should be deleted (using snap delete ). After deleting some snapshots, it may make sense to alter the volume's snapshot schedule (using snap schedule ) to reduce the number of snapshots that are kept on line.

The following example shows file system inode usage for a specified volume: 

  toaster> df -i /vol/vol0
  Filesystem          iused    ifree    %iused  Mounted on
  /vol/vol0           164591   14313    92%     /vol/vol0

You can increase the number of inodes in a file system at any time using the maxfiles command (see maxfiles(1)).

VFILER CONSIDERATIONS

When run from a vfiler context, (e.g. via the vfiler run command), df displays information about only those filesystems that are owned by the concerned vfiler.

SEE ALSO

na_maxfiles(1), na_rc(5), na_snap(1)

BUGS

On some NFS clients, the df command does not follow the NFS protocol specification correctly and may display incorrect information about the size of large file systems. Some versions report negative file system sizes; others report a maximum file system size of 2 GB, no matter how large the file system actually is.

Table of Contents