Re: tar extract errors occurring rarely but with same symptoms

[Paul Eggert]

On 6/5/21 10:23 PM, Daniel Villeneuve wrote:

> openat(AT_FDCWD, "XXXXXX_config/static/users", O_WRONLY|O_CREAT|O_EXCL, 
> 000) = 4
> fstat(4, {st_mode=S_IFREG|000, st_size=0, ...}) = 0
> close(4)                                = 0

OK, so at this point the newly-created file XXXXXX_config/static/users 
must exist as a regular file.

> newfstatat(AT_FDCWD, "XXXXXX_config/static/users", 0x7ffc9b136f50, 
> AT_SYMLINK_NOFOLLOW) = -1 ENOENT (No such file or directory)

And yet here, the same file does not exist.

What happened between those two syscalls, which caused the file to no 
longer exist? Can you find all mentions of that file in the trace of the 
failed 'tar'?