xref: /freebsd/bin/df/df.1 (revision 71fe318b852b8dfb3e799cb12ef184750f7f8eac)
1.\" Copyright (c) 1989, 1990, 1993
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.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)df.1	8.3 (Berkeley) 5/8/95
33.\" $FreeBSD$
34.\"
35.Dd May 8, 1995
36.Dt DF 1
37.Os
38.Sh NAME
39.Nm df
40.Nd display free disk space
41.Sh SYNOPSIS
42.Nm
43.Oo
44.Fl b | h | H | k |
45.Fl m | P
46.Oc
47.Op Fl ailn
48.Op Fl t Ar type
49.Op Ar file | filesystem ...
50.Sh DESCRIPTION
51The
52.Nm
53utility
54displays statistics about the amount of free disk space on the specified
55.Ar file system
56or on the file system of which
57.Ar file
58is a part.
59Values are displayed in 512-byte per block counts.
60If neither a file or a file system operand is specified,
61statistics for all mounted file systems are displayed
62(subject to the
63.Fl t
64option below).
65.Pp
66The following options are available:
67.Bl -tag -width Ds
68.It Fl a
69Show all mount points, including those that were mounted with the MNT_IGNORE
70flag.
71.It Fl b
72Use 512-byte blocks rather than the default.  Note that
73this overrides the
74.Ev BLOCKSIZE
75specification from the environment.
76.It Fl g
77Use 1073741824-byte (1-Gbyte) blocks rather than the default.  Note that
78this overrides the
79.Ev BLOCKSIZE
80specification from the environment.
81.It Fl H
82"Human-readable" output.  Use unit suffixes: Byte, Kilobyte, Megabyte,
83Gigabyte, Terabyte and Petabyte in order to reduce the number of
84digits to three or less using base 10 for sizes.
85.It Fl h
86"Human-readable" output.  Use unit suffixes: Byte, Kilobyte, Megabyte,
87Gigabyte, Terabyte and Petabyte in order to reduce the number of
88digits to three or less using base 2 for sizes.
89.It Fl i
90Include statistics on the number of free inodes.
91.It Fl k
92Use 1024-byte (1-Kbyte) blocks rather than the default.  Note that
93this overrides the
94.Ev BLOCKSIZE
95specification from the environment.
96.It Fl l
97Only display information about locally-mounted file systems.
98.It Fl m
99Use 1048576-byte (1-Mbyte) blocks rather than the default.  Note that
100this overrides the
101.Ev BLOCKSIZE
102specification from the environment.
103.It Fl n
104Print out the previously obtained statistics from the file systems.
105This option should be used if it is possible that one or more
106file systems are in a state such that they will not be able to provide
107statistics without a long delay.
108When this option is specified,
109.Nm
110will not request new statistics from the file systems, but will respond
111with the possibly stale statistics that were previously obtained.
112.It Fl P
113Use POSIX compliant output of 512-byte blocks rather than the default.
114Note that this overrides the
115.Ev BLOCKSIZE
116specification from the environment.
117.It Fl t
118Only print out statistics for file systems of the specified types.
119More than one type may be specified in a comma separated list.
120The list of file system types can be prefixed with
121.Dq no
122to specify the file system types for which action should
123.Em not
124be taken.
125For example, the
126.Nm
127command:
128.Bd -literal -offset indent
129df -t nonfs,nullfs
130.Ed
131.Pp
132lists all file systems except those of type
133.Tn NFS
134and
135.Tn NULLFS .
136The
137.Xr lsvfs 1
138command can be used to find out the types of file systems
139that are available on the system.
140.El
141.Sh ENVIRONMENT
142.Bl -tag -width BLOCKSIZE
143.It Ev BLOCKSIZE
144If the environment variable
145.Ev BLOCKSIZE
146is set, the block counts will be displayed in units of that size block.
147.El
148.Sh BUGS
149The
150.Fl n
151and
152.Fl t
153flags are ignored if a file or file system is specified.
154.Sh SEE ALSO
155.Xr lsvfs 1 ,
156.Xr quota 1 ,
157.Xr fstatfs 2 ,
158.Xr getfsstat 2 ,
159.Xr statfs 2 ,
160.Xr getmntinfo 3 ,
161.Xr fstab 5 ,
162.Xr mount 8 ,
163.Xr quot 8
164.Sh HISTORY
165A
166.Nm
167command appeared in
168.At v1 .
169