effect of strip(1) on du(1)

[Subbsd]

On Fri, Mar 3, 2017 at 2:04 AM, Peter Jeremy <peter at rulingia.com> wrote:
> On 2017-Mar-02 22:29:46 +0300, Subbsd <subbsd at gmail.com> wrote:
>>During some interval after strip call, du will show 512B for any file.
>>If execute du(1) after strip(1) without delay, this behavior is reproduced 100%:
>
> What filesystem are you using?  strip(1) rewrites the target file and du(1)
> reports the number of blocks reported by stat(2).  It seems that you are
> hitting a situation where the file metadata isn't immediately updated.
>
> --
> Peter Jeremy


Got it. My filesystem is ZFS. Looks like when ZFS open and write data
to file, we get wrong number of blocks during a small interval after
writing. Thanks for pointing this out!