You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is a bug (or missing feature) in the WinFsp FUSE API. It seems that the hardlink count returned from a getattr call isn't propagated to the Windows filesystem layer (i.e. nNumberOfLinks in BY_HANDLE_FILE_INFORMATION always reads 1).
How to Reproduce
Use a filesystem that returns st_nlink > 1 in getattr. Checking with the stat tool I can see that two files share the same inode, but each of them has their link count reported as 1 (even though st_nlink is actually 3):
Bug Report
I believe this is a bug (or missing feature) in the WinFsp FUSE API. It seems that the hardlink count returned from a
getattr
call isn't propagated to the Windows filesystem layer (i.e.nNumberOfLinks
inBY_HANDLE_FILE_INFORMATION
always reads1
).How to Reproduce
Use a filesystem that returns
st_nlink > 1
ingetattr
. Checking with thestat
tool I can see that two files share the same inode, but each of them has their link count reported as1
(even thoughst_nlink
is actually3
):At the same time, logging from the
getattr
operation shows thatst_nlink
is returned as3
:Behaviors
I'd expect
stat
to report the correct hardlink count.Environment
The text was updated successfully, but these errors were encountered: