{
    "content": [
        {
            "type": "text",
            "text": "# df (info)\n\n## Sections\n\n- **File: coreutils.info,  Node: df invocation,  Next: du invocation,  Up: Disk usage** (1 subsections)\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "df",
        "section": "",
        "mode": "info",
        "summary": null,
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "File: coreutils.info,  Node: df invocation,  Next: du invocation,  Up: Disk usage",
                "lines": 1,
                "subsections": [
                    {
                        "name": "14.1 'df': Report file system disk space usage",
                        "lines": 238
                    }
                ]
            }
        ],
        "sections": {
            "File: coreutils.info,  Node: df invocation,  Next: du invocation,  Up: Disk usage": {
                "content": "",
                "subsections": [
                    {
                        "name": "14.1 'df': Report file system disk space usage",
                        "content": "'df' reports the amount of disk space used and available on file\nsystems.  Synopsis:\n\ndf [OPTION]... [FILE]...\n\nWith no arguments, 'df' reports the space used and available on all\ncurrently mounted file systems (of all types).  Otherwise, 'df' reports\non the file system containing each argument FILE.\n\nNormally the disk space is printed in units of 1024 bytes, but this\ncan be overridden (*note Block size::).  Non-integer quantities are\nrounded up to the next higher unit.\n\nFor bind mounts and without arguments, 'df' only outputs the\nstatistics for that device with the shortest mount point name in the\nlist of file systems (MTAB), i.e., it hides duplicate entries, unless\nthe '-a' option is specified.\n\nWith the same logic, 'df' elides a mount entry of a dummy pseudo\ndevice if there is another mount entry of a real block device for that\nmount point with the same device number, e.g.  the early-boot pseudo\nfile system 'rootfs' is not shown per default when already the real root\ndevice has been mounted.\n\nIf an argument FILE resolves to a special file containing a mounted\nfile system, 'df' shows the space available on that file system rather\nthan on the file system containing the device node.  GNU 'df' does not\nattempt to determine the disk usage on unmounted file systems, because\non most kinds of systems doing so requires extremely nonportable\nintimate knowledge of file system structures.\n\nThe program accepts the following options.  Also see *note Common\noptions::.\n\n'-a'\n'--all'\nInclude in the listing dummy, duplicate, or inaccessible file\nsystems, which are omitted by default.  Dummy file systems are\ntypically special purpose pseudo file systems such as '/proc', with\nno associated storage.  Duplicate file systems are local or remote\nfile systems that are mounted at separate locations in the local\nfile hierarchy, or bind mounted locations.  Inaccessible file\nsystems are those which are mounted but subsequently over-mounted\nby another file system at that point, or otherwise inaccessible due\nto permissions of the mount point etc.\n\n'-B SIZE'\n'--block-size=SIZE'\nScale sizes by SIZE before printing them (*note Block size::).  For\nexample, '-BG' prints sizes in units of 1,073,741,824 bytes.\n\n'-h'\n'--human-readable'\nAppend a size letter to each size, such as 'M' for mebibytes.\nPowers of 1024 are used, not 1000; 'M' stands for 1,048,576 bytes.\nThis option is equivalent to '--block-size=human-readable'.  Use\nthe '--si' option if you prefer powers of 1000.\n\n'-H'\nEquivalent to '--si'.\n\n'-i'\n'--inodes'\nList inode usage information instead of block usage.  An inode\n(short for index node) contains information about a file such as\nits owner, permissions, timestamps, and location on the disk.\n\n'-k'\nPrint sizes in 1024-byte blocks, overriding the default block size\n(*note Block size::).  This option is equivalent to\n'--block-size=1K'.\n\n'-l'\n'--local'\nLimit the listing to local file systems.  By default, remote file\nsystems are also listed.\n\n'--no-sync'\nDo not invoke the 'sync' system call before getting any usage data.\nThis may make 'df' run significantly faster on systems with many\ndisks, but on some systems (notably SunOS) the results may be\nslightly out of date.  This is the default.\n\n'--output'\n'--output[=FIELDLIST]'\nUse the output format defined by FIELDLIST, or print all fields if\nFIELDLIST is omitted.  In the latter case, the order of the\ncolumns conforms to the order of the field descriptions below.\n\nThe use of the '--output' together with each of the options '-i',\n'-P', and '-T' is mutually exclusive.\n\nFIELDLIST is a comma-separated list of columns to be included in\n'df''s output and therefore effectively controls the order of\noutput columns.  Each field can thus be used at the place of\nchoice, but yet must only be used once.\n\nValid field names in the FIELDLIST are:\n'source'\nThe source of the mount point, usually a device.\n'fstype'\nFile system type.\n\n'itotal'\nTotal number of inodes.\n'iused'\nNumber of used inodes.\n'iavail'\nNumber of available inodes.\n'ipcent'\nPercentage of IUSED divided by ITOTAL.\n\n'size'\nTotal number of blocks.\n'used'\nNumber of used blocks.\n'avail'\nNumber of available blocks.\n'pcent'\nPercentage of USED divided by SIZE.\n\n'file'\nThe file name if specified on the command line.\n'target'\nThe mount point.\n\nThe fields for block and inodes statistics are affected by the\nscaling options like '-h' as usual.\n\nThe definition of the FIELDLIST can even be split among several\n'--output' uses.\n\n#!/bin/sh\n# Print the TARGET (i.e., the mount point) along with their percentage\n# statistic regarding the blocks and the inodes.\ndf --out=target --output=pcent,ipcent\n\n# Print all available fields.\ndf --o\n\n'-P'\n'--portability'\nUse the POSIX output format.  This is like the default format\nexcept for the following:\n\n1. The information about each file system is always printed on\nexactly one line; a mount device is never put on a line by\nitself.  This means that if the mount device name is more than\n20 characters long (e.g., for some network mounts), the\ncolumns are misaligned.\n\n2. The labels in the header output line are changed to conform to\nPOSIX.\n\n3. The default block size and output format are unaffected by the\n'DFBLOCKSIZE', 'BLOCKSIZE' and 'BLOCKSIZE' environment\nvariables.  However, the default block size is still affected\nby 'POSIXLYCORRECT': it is 512 if 'POSIXLYCORRECT' is set,\n1024 otherwise.  *Note Block size::.\n\n'--si'\nAppend an SI-style abbreviation to each size, such as 'M' for\nmegabytes.  Powers of 1000 are used, not 1024; 'M' stands for\n1,000,000 bytes.  This option is equivalent to '--block-size=si'.\nUse the '-h' or '--human-readable' option if you prefer powers of\n1024.\n\n'--sync'\nInvoke the 'sync' system call before getting any usage data.  On\nsome systems (notably SunOS), doing this yields more up to date\nresults, but in general this option makes 'df' much slower,\nespecially when there are many or very busy file systems.\n\n'--total'\nPrint a grand total of all arguments after all arguments have been\nprocessed.  This can be used to find out the total disk size, usage\nand available space of all listed devices.  If no arguments are\nspecified df will try harder to elide file systems insignificant to\nthe total available space, by suppressing duplicate remote file\nsystems.\n\nFor the grand total line, 'df' prints '\"total\"' into the SOURCE\ncolumn, and '\"-\"' into the TARGET column.  If there is no SOURCE\ncolumn (see '--output'), then 'df' prints '\"total\"' into the TARGET\ncolumn, if present.\n\n'-t FSTYPE'\n'--type=FSTYPE'\nLimit the listing to file systems of type FSTYPE.  Multiple file\nsystem types can be specified by giving multiple '-t' options.  By\ndefault, nothing is omitted.\n\n'-T'\n'--print-type'\nPrint each file system's type.  The types printed here are the same\nones you can include or exclude with '-t' and '-x'.  The particular\ntypes printed are whatever is supported by the system.  Here are\nsome of the common names (this list is certainly not exhaustive):\n\n'nfs'\nAn NFS file system, i.e., one mounted over a network from\nanother machine.  This is the one type name which seems to be\nused uniformly by all systems.\n\n'ext2, ext3, ext4, xfs, btrfs...'\nA file system on a locally-mounted hard disk.  (The system\nmight even support more than one type here; Linux does.)\n\n'iso9660, cdfs'\nA file system on a CD or DVD drive.  HP-UX uses 'cdfs', most\nother systems use 'iso9660'.\n\n'ntfs,fat'\nFile systems used by MS-Windows / MS-DOS.\n\n'-x FSTYPE'\n'--exclude-type=FSTYPE'\nLimit the listing to file systems not of type FSTYPE.  Multiple\nfile system types can be eliminated by giving multiple '-x'\noptions.  By default, no file system types are omitted.\n\n'-v'\nIgnored; for compatibility with System V versions of 'df'.\n\n'df' is installed only on systems that have usable mount tables, so\nportable scripts should not rely on its existence.\n\nAn exit status of zero indicates success, and a nonzero value\nindicates failure.  Failure includes the case where no output is\ngenerated, so you can inspect the exit status of a command like 'df -t\next3 -t reiserfs DIR' to test whether DIR is on a file system of type\n'ext3' or 'reiserfs'.\n\nSince the list of file systems (MTAB) is needed to determine the file\nsystem type, failure includes the cases when that list cannot be read\nand one or more of the options '-a', '-l', '-t' or '-x' is used together\nwith a file name argument.\n"
                    }
                ]
            }
        }
    }
}