Skip to main content

du command man page

DU(1) User Commands DU(1)

       du - estimate file space usage

       du [OPTION]... [FILE]...
       du [OPTION]... --files0-from=F

       Summarize disk usage of each FILE, recursively for directories.

       Mandatory  arguments  to long  options are mandatory for short options

       -a, --all
     write counts for all files, not just directories

     print apparent sizes,  rather  than  disk usage; although  the
     apparent size is usually smaller, it may be larger due to holes
     in (‘sparse’) files, internal  fragmentation,  indirect  blocks,
     and the like

       -B, --block-size=SIZE use SIZE-byte blocks

       -b, --bytes
     equivalent to ‘--apparent-size --block-size=1’

       -c, --total
     produce a grand total

       -D, --dereference-args
     dereference FILEs that are symbolic links

     summarize disk usage of the NUL-terminated file names specified
     in file F

       -H     like --si, but also evokes a warning; will  soon change to  be
     equivalent to --dereference-args (-D)

       -h, --human-readable
     print sizes in human readable format (e.g., 1K 234M 2G)

       --si   like -h, but use powers of 1000 not 1024

       -k     like --block-size=1K

       -l, --count-links
     count sizes many times if hard linked

       -m     like --block-size=1M

       -L, --dereference
     dereference all symbolic links

       -P, --no-dereference
     don’t follow any symbolic links (this is the default)

       -0, --null
     end each output line with 0 byte rather than newline

       -S, --separate-dirs
     do not include size of subdirectories

       -s, --summarize
     display only a total for each argument

       -x, --one-file-system
     skip directories on different file systems

       -X FILE, --exclude-from=FILE
     Exclude files that match any pattern in FILE.

       --exclude=PATTERN Exclude files that match PATTERN.

     print the total for a directory (or file, with --all) only if it
     is  N  or fewer levels below  the  command   line   argument;
     --max-depth=0 is the same as --summarize

       --time show time of the last modification of any file in the directory,
     or any of its subdirectories

     show time as WORD instead of modification time:  atime,  access,
     use, ctime or status

       --time-style=STYLE show times using style STYLE:
     full-iso, long-iso,  iso,  +FORMAT  FORMAT  is interpreted like

       --help display this help and exit

     output version information and exit

       SIZE may be (or may be an integer optionally followed by) one  of  fol-
       lowing: kB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on for G, T,
       P, E, Z, Y.

       PATTERN is a shell pattern (not a regular expression).  The  pattern  ?
       matches any  one  character, whereas * matches any string (composed of
       zero, one or multiple characters).  For example, *.o  will  match  any
       files whose names end in .o.  Therefore, the command

     du --exclude=’*.o’

       will skip all files and subdirectories ending in .o (including the file
       .o itself).

       Written by Torbjorn Granlund, David MacKenzie,  Paul  Eggert,  and  Jim

       Report bugs to <>.

       Copyright © 2006 Free Software Foundation, Inc.
       This  is free  software.   You may redistribute copies of it under the
       terms  of  the   GNU    General  Public       License
       <>. There is NO WARRANTY, to the
       extent permitted by law.

       The full documentation for du is maintained as a Texinfo  manual.   If
       the  info and du programs are properly installed at your site, the com-

     info du

       should give you access to the complete manual.

du 5.97   May 2011 DU(1)


Popular posts from this blog

Find and replace with sed command in Linux

Find and replace feature is always handy. It can turn into a torture when it comes to change or delete a simple constant string in a text file. There is a handy tool in linux for doing these kind of tihngs. Actually sed is not a text editor but it is used outside of the text file to make changes.

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector.
Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true) and combines them with the previous line that starts with a date pattern.

server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n
Logstash filter: