On Tue, Mar 10, 2020 at 12:24 PM Kaz Kylheku (Coreutils) <962-396-1...@kylheku.com> wrote: > On 2020-03-10 11:52, Jim Meyering wrote: > > Otherwise, du provides no way of seeing how much of the actual disk > > space is being used by such FS-compressed files. > > If you stat the file, what are the values of st_size, st_blksize and > st_blocks?
That particular file is long gone, but I've just created a 1.8T file on a 700G file system. Before I began this experiment, "Avail" was 524G, so it appears to occupy about 60G actual space. FTR, I created the file by running this: yes $(printf '%065535d\n' 0) > big $ stat big File: big Size: 1957123607586 Blocks: 3822507048 IO Block: 4096 regular file Device: 1bh/27d Inode: 788544108 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 6405/meyering) Gid: ( 100/ users) Access: 2020-03-10 21:01:17.710555709 -0700 Modify: 2020-03-10 21:26:05.137122240 -0700 Change: 2020-03-10 21:26:05.137122240 -0700 Birth: - $ du -sh big; df -hT . 1.8T big Filesystem Type Size Used Avail Use% Mounted on /dev/vda3 btrfs 698G 221G 464G 33% /home/meyering
