=head1 NAMEB<ncdu> - NCurses Disk Usage=head1 SYNOPSISB<ncdu> [I<options>] I<dir>=head1 DESCRIPTIONncdu (NCurses Disk Usage) is a curses-based version of the well-known 'du', andprovides a fast way to see what directories are using your disk space.=head1 OPTIONS=head2 Mode Selection=over=item B<-h>, B<--help>Print a short help message and quit.=item B<-v>, B<-V>, B<--version>Print ncdu version and quit.=item B<-f> I<FILE>Load the given file, which has earlier been created with the C<-o> option. IfI<FILE> is equivalent to C<->, the file is read from standard input.For the sake of preventing a screw-up, the current version of ncdu will assumethat the directory information in the imported file does not represent thefilesystem on which the file is being imported. That is, the refresh, filedeletion and shell spawning options in the browser will be disabled.=item I<dir>Scan the given directory.=item B<-o> I<FILE>Export all necessary information to I<FILE> instead of opening the browserinterface. If I<FILE> is C<->, the data is written to standard output. See theexamples section below for some handy use cases.Be warned that the exported data may grow quite large when exporting adirectory with many files. 10.000 files will get you an export in the order of600 to 700 KiB uncompressed, or a little over 100 KiB when compressed withgzip. This scales linearly, so be prepared to handle a few tens of megabyteswhen dealing with millions of files.=item B<-e>Enable extended information mode. This will, in addition to the usual fileinformation, also read the ownership, permissions and last modification timefor each file. This will result in higher memory usage (by roughly ~30%) and ina larger output file when exporting.When using the file export/import function, this flag will need to be addedboth when exporting (to make sure the information is added to the export), andwhen importing (to read this extra information in memory). This flag has noeffect when importing a file that has been exported without the extendedinformation.This enables viewing and sorting by the latest child mtime, or modified time,using 'm' and 'M', respectively.=back=head2 Interface options=over=item B<-0>Don't give any feedback while scanning a directory or importing a file, otherthan when a fatal error occurs. Ncurses will not be initialized until the scanis complete. When exporting the data with C<-o>, ncurses will not beinitialized at all. This option is the default when exporting to standardoutput.=item B<-1>Similar to C<-0>, but does give feedback on the scanning progress with a singleline of output. This option is the default when exporting to a file.In some cases, the ncurses browser interface which you'll see after thescan/import is complete may look garbled when using this option. If you're notexporting to a file, C<-2> is probably a better choice.=item B<-2>Provide a full-screen ncurses interface while scanning a directory or importinga file. This is the only interface that provides feedback on any non-fatalerrors while scanning.=item B<-q>Quiet mode. While scanning or importing the directory, ncdu will update thescreen 10 times a second by default, this will be decreased to once every 2seconds in quiet mode. Use this feature to save bandwidth over remoteconnections. This option has no effect when C<-0> is used.=item B<-r>Read-only mode. This will disable the built-in file deletion feature. Thisoption has no effect when C<-o> is used, because there will not be a browserinterface in that case. It has no effect when C<-f> is used, either, becausethe deletion feature is disabled in that case anyway.WARNING: This option will only prevent deletion through the file browser. It isstill possible to spawn a shell from ncdu and delete or modify files fromthere. To disable that feature as well, pass the C<-r> option twice (seeC<-rr>).=item B<-rr>In addition to C<-r>, this will also disable the shell spawning feature of thefile browser.=item B<--si>List sizes using base 10 prefixes, that is, powers of 1000 (KB, MB, etc), asdefined in the International System of Units (SI), instead of the usual base 2prefixes, that is, powers of 1024 (KiB, MiB, etc).=item B<--confirm-quit>Requires a confirmation before quitting ncdu. Very helpful when youaccidentally press 'q' during or after a very long scan.=item B<--color> I<SCHEME>Select a color scheme. The following schemes are recognized: I<off> to disablecolors, I<dark> for a color scheme intended for dark backgrounds and I<dark-bg>for a variation of the I<dark> color scheme that also works in terminals with alight background.The default is I<dark-bg> unless the C<NO_COLOR> environment variable is set.=back=head2 Scan OptionsThese options affect the scanning progress, and have no effect when importingdirectory information from a file.=over=item B<-x>Do not cross filesystem boundaries, i.e. only count files and directories onthe same filesystem as the directory being scanned.=item B<--exclude> I<PATTERN>Exclude files that match I<PATTERN>. The files will still be displayed bydefault, but are not counted towards the disk usage statistics. This argumentcan be added multiple times to add more patterns.=item B<-X> I<FILE>, B<--exclude-from> I<FILE>Exclude files that match any pattern in I<FILE>. Patterns should be separatedby a newline.=item B<--exclude-caches>Exclude directories containing CACHEDIR.TAG. The directories will still bedisplayed, but not their content, and they are not counted towards the diskusage statistics.See http://www.brynosaurus.com/cachedir/=item B<-L>, B<--follow-symlinks>Follow symlinks and count the size of the file they point to. As of ncdu 1.14,this option will not follow symlinks to directories and will count eachsymlinked file as a unique file (i.e. unlike how hard links are handled). Thisis subject to change in later versions.=item B<--exclude-firmlinks>(MacOS only) Exclude firmlinks.=item B<--exclude-kernfs>(Linux only) Exclude Linux pseudo filesystems, e.g. /proc (procfs), /sys (sysfs).The complete list of currently known pseudo filesystems is: binfmt, bpf, cgroup,cgroup2, debug, devpts, proc, pstore, security, selinux, sys, trace.=back=head1 KEYS=over=item B<?>Show help + keys + about screen=item B<up>, B<down>, B<j>, B<k>Cycle through the items=item B<right>, B<enter>, B<l>Open selected directory=item B<left>, B<<>, B<h>Go to parent directory=item B<n>Order by filename (press again for descending order)=item B<s>Order by filesize (press again for descending order)=item B<C>Order by number of items (press again for descending order)=item B<a>Toggle between showing disk usage and showing apparent size.=item B<M>Order by latest child mtime, or modified time. (press again for descending order)Requires the -e flag.=item B<d>Delete the selected file or directory. An error message will be shown when thecontents of the directory do not match or do not exist anymore on thefilesystem.=item B<t>Toggle dirs before files when sorting.=item B<g>Toggle between showing percentage, graph, both, or none. Percentage is relativeto the size of the current directory, graph is relative to the largest item inthe current directory.=item B<c>Toggle display of child item counts.=item B<m>Toggle display of latest child mtime, or modified time. Requires the -e flag.=item B<e>Show/hide 'hidden' or 'excluded' files and directories. Please note that eventhough you can't see the hidden files and directories, they are still there andthey are still included in the directory sizes. If you suspect that the totalsshown at the bottom of the screen are not correct, make sure you haven'tenabled this option.=item B<i>Show information about the current selected item.=item B<r>Refresh/recalculate the current directory.=item B<b>Spawn shell in current directory.Ncdu will determine your preferred shell from the C<NCDU_SHELL> or C<SHELL>variable (in that order), or will call C</bin/sh> if neither are set. Thisallows you to also configure another command to be run when he 'b' key ispressed. For example, to spawn the L<vifm(1)> file manager instead of a shell,run ncdu as follows:export NCDU_SHELL=vifmncduNcdu will set the C<NCDU_LEVEL> environment variable or increment it beforespawning the shell. This variable allows you to detect when your shell isrunning from within ncdu, which can be useful to avoid nesting multipleinstances of ncdu. Ncdu itself does not (currently) warn when attempting to runnested instances.=item B<q>Quit=back=head1 FILE FLAGSEntries in the browser interface may be prefixed by a one-character flag. Theseflags have the following meaning:=over=item B<!>An error occurred while reading this directory.=item B<.>An error occurred while reading a subdirectory, so the indicated size may not becorrect.=item B<<>File or directory is excluded from the statistics by using exclude patterns.=item B<< > >>Directory is on another filesystem.=item B<^>Directory is excluded from the statistics due to being a Linux pseudo filesystem.=item B<@>This is neither a file nor a folder (symlink, socket, ...).=item B<H>Same file was already counted (hard link).=item B<e>Empty directory.=back=head1 EXAMPLESTo scan and browse the directory you're currently in, all you need is a simple:ncduIf you want to scan a full filesystem, your root filesystem, for example, thenyou'll want to use C<-x>:ncdu -x /Since scanning a large directory may take a while, you can scan a directory andexport the results for later viewing:ncdu -1xo- / | gzip >export.gz# ...some time later:zcat export.gz | ncdu -f-To export from a cron job, make sure to replace C<-1> with C<-0> to suppressany unnecessary output.You can also export a directory and browse it once scanning is done:ncdu -o- | tee export.file | ./ncdu -f-The same is possible with gzip compression, but is a bit kludgey:ncdu -o- | gzip | tee export.gz | gunzip | ./ncdu -f-To scan a system remotely, but browse through the files locally:ssh -C user@system ncdu -o- / | ./ncdu -f-The C<-C> option to ssh enables compression, which will be very useful overslow links. Remote scanning and local viewing has two major advantages whencompared to running ncdu directly on the remote system: You can browse throughthe scanned directory on the local system without any network latency, and ncdudoes not keep the entire directory structure in memory when exporting, so youwon't consume much memory on the remote system.=head1 HARD LINKSEvery disk usage analysis utility has its own way of (not) counting hard links.There does not seem to be any universally agreed method of handling hard links,and it is even inconsistent among different versions of ncdu. This sectionexplains what each version of ncdu does.ncdu 1.5 and below does not support any hard link detection at all: each linkis considered a separate inode and its size is counted for every link. Thismeans that the displayed directory sizes are incorrect when analyzingdirectories which contain hard links.ncdu 1.6 has basic hard link detection: When a link to a previously encounteredinode is detected, the link is considered to have a file size of zero bytes.Its size is not counted again, and the link is indicated in the browserinterface with a 'H' mark. The displayed directory sizes are only correct whenall links to an inode reside within that directory. When this is not the case,the sizes may or may not be correct, depending on which links were consideredas "duplicate" and which as "original". The indicated size of the topmostdirectory (that is, the one specified on the command line upon starting ncdu)is always correct.ncdu 1.7 and later has improved hard link detection. Each file that has morethan two links has the "H" mark visible in the browser interface. Each hardlink is counted exactly once for every directory it appears in. The indicatedsize of each directory is therefore, correctly, the sum of the sizes of allunique inodes that can be found in that directory. Note, however, that this maynot always be same as the space that will be reclaimed after deleting thedirectory, as some inodes may still be accessible from hard links outside it.=head1 BUGSDirectory hard links are not supported. They will not be detected as being hardlinks, and will thus be scanned and counted multiple times.Some minor glitches may appear when displaying filenames that contain multibyteor multicolumn characters.All sizes are internally represented as a signed 64bit integer. If you have adirectory larger than 8 EiB minus one byte, ncdu will clip its size to 8 EiBminus one byte. When deleting items in a directory with a clipped size, theresulting sizes will be incorrect.Item counts are stored in a signed 32-bit integer without overflow detection.If you have a directory with more than 2 billion files, quite literallyanything can happen.On macOS 10.15 and later, running ncdu on the root directory without`--exclude-firmlinks` may cause directories to be scanned and counted multipletimes. Firmlink cycles are currently (1.16) not detected, so it may also causencdu to get stuck in an infinite loop and eventually run out of memory.Please report any other bugs you may find at the bug tracker, which can befound on the web site at https://dev.yorhel.nl/ncdu=head1 AUTHORWritten by Yoran Heling <projects@yorhel.nl>.=head1 SEE ALSOL<du(1)>