Open adammoody opened 2 years ago
Actually it seems, cp -p
calls futimens
. I added wrappers for this and and "not supported" wrapper for utimensat
in https://github.com/LLNL/UnifyFS/commit/64977810a18351ed438bb59cff791943ea55636e
Noticing a segfault on a touch /unifyfs/file1
:
2022-08-05T13:14:54 tid=51630 @ __wrap_close() [unifyfs-sysio.c:2287] closing (internal=0, exposed=1024)
2022-08-05T13:14:54 tid=51630 @ __wrap_close() [unifyfs-sysio.c:2324] syncing fid=1
2022-08-05T13:14:54 tid=51630 @ unifyfs_intercept_fd() [posix_client.c:289] Changing fd from exposed dup2=0 to internal 0
./runme_preload: line 68: 51630 Segmentation fault (core dumped) touch /unifyfs/file1
A
cp
with the-p
option fails when accessing a file descriptor while trying to copy the file timestamps. Here is an strace output forcp -pr file.foo file.bar
on NFS.It looks to be due to a missing wrapper for
utimensat
.We should also check
fadvise64
,fgetxattr
,fgetxattr
.