New ncdu, ncdc + btrfssize + misc changes
This commit is contained in:
parent
7cf772d968
commit
07143cfb36
17 changed files with 182 additions and 84 deletions
|
|
@ -29,7 +29,7 @@ the existing format.
|
|||
=head2 Metadata
|
||||
|
||||
The C<< <metadata> >> element is a JSON object holding whatever (short)
|
||||
metadata you'd want. This block is currently (1.9-1.11) ignored by ncdu when
|
||||
metadata you'd want. This block is currently (1.9-1.12) ignored by ncdu when
|
||||
importing, but it writes out the following keys when exporting:
|
||||
|
||||
=over
|
||||
|
|
@ -109,7 +109,7 @@ C<< 0 <= dev < 2^64 >>.
|
|||
Number. Inode number as reported by C<lstat().st_ino>. Together with the Device
|
||||
ID this uniquely identifies a file in this dump. In the case of hard links, two
|
||||
objects may appear with the same (C<dev>,C<ino>) combination. A value of 0 is
|
||||
assumed if this field is absent. This is currently (ncdu 1.9-1.11) not a
|
||||
assumed if this field is absent. This is currently (ncdu 1.9-1.12) not a
|
||||
problem as long as the C<hlnkc> field is false, otherwise it will consider
|
||||
everything with the same C<dev> and empty C<ino> values as a single hardlinked
|
||||
file. Accepted values are in the range of C<< 0 <= ino < 2^64 >>.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue