bug#34173: Tail File System Error on overlayfs

2019-01-22 Thread Bernhard Voelker
On 1/22/19 9:03 PM, m...@nerdcore.net wrote: > tail: unrecognized file system type 0x794c7630 for > '/var/log/nginx/error.log'. please report this to bug-coreutils@gnu.org. > reverting to polling Thank you for the report. This has been fixed in coreutils version 8.25 - meaning you are likely

bug#34110: feature request: dual-column du output, showing "real" and "on-disk" sizes (and about that "apparent-size" concept)

2019-01-22 Thread Paul Eggert
On 1/22/19 2:40 PM, Bernhard Voelker wrote: This sounds to me as if you wanted 'du' to read() the content of each file to get the 'correct' statistics. That is more in the domain of wc(1). du already has an --apparent-size option that gives the same size that 'read' would give. As I

bug#34173: Tail File System Error on overlayfs

2019-01-22 Thread mike
I'm using a Docker environment which has a rootfs mounted using the "overlay" filesystem on Linux kernel 4.4.0-141-generic (Ubuntu 16.04) on amd64. Inside the Docker environment I tried the usual "tail follow" command: tail -f /var/log/nginx/error.log This spat out the error message: ==>

bug#34110: feature request: dual-column du output, showing "real" and "on-disk" sizes (and about that "apparent-size" concept)

2019-01-22 Thread Bernhard Voelker
On 1/17/19 11:13 AM, René J.V. Bertin wrote: > I realise that you cannot really call the content size observable "real size > when reporting from a disk-usage viewpoint, but "content size" > (--content-size, -C) should be clear enough? This sounds to me as if you wanted 'du' to read() the content