PageRenderTime 18ms CodeModel.GetById 15ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/bin/df/df.1

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