ncdu 1.21 + 2.7
This commit is contained in:
parent
68bf70e0eb
commit
76b8f42f1d
32 changed files with 171 additions and 24 deletions
|
|
@ -196,6 +196,10 @@ prev
|
|||
absent if this is the first item in a directory. This field forms a
|
||||
singly-linked list of all items in a directory.
|
||||
|
||||
BUG: ncdu 2.6 incorrectly outputs a root item with prev=0. The root item is
|
||||
not supposed to be part of a directory and this field is properly absent in
|
||||
later versions.
|
||||
|
||||
**Fields for type >= 0**
|
||||
|
||||
asize
|
||||
|
|
@ -350,15 +354,14 @@ Data block size
|
|||
|
||||
Testing
|
||||
: If you're implementing a custom writer for this format, make sure to check
|
||||
out the
|
||||
[ncdubinexp.pl](https://code.blicky.net/yorhel/ncdu/src/ncdubinexp.pl)
|
||||
script in the git repository. Ncdu only reads the parts of a file that it
|
||||
actually needs, so passing a file to ncdu is no guarantee that it is
|
||||
well-formed. The ncdubinexp.pl script is more thorough in validating file
|
||||
correctness but misses a few invariants that ncdu does check for, so
|
||||
the best way to verify a file is to run both:
|
||||
out the 'validate' subcommand of
|
||||
[ncdutils](https://code.blicky.net/yorhel/ncdutils). Ncdu only reads the
|
||||
parts of a file that it actually needs, so passing a file to ncdu is no
|
||||
guarantee that it is well-formed. ncdutils is more thorough:
|
||||
|
||||
```
|
||||
ncdu -o/dev/null -f file.ncdu # Read entire tree and export to /dev/null
|
||||
ncdubinfmt.pl <file.ncdu # Read and verify the entire file
|
||||
ncdutils validate file.ncdu
|
||||
```
|
||||
|
||||
Passing `--list-blocks` and `--list-items` may also be useful for
|
||||
diagnostics.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue