Export FAT32 share (which does not support reparse points) and try to create symlink, fifo or socket. Compound request will try to create empty file, attach reparse point to it, and then close it. On FAT32 this the attach reparse point part will fail and returns error, letting the empty file created on the disk. Later the code is trying to remove this empty file, but it is racy as meanwhile other client may open that empty file and hence block its removal. So the idea for this is simple: If filesystem share does not support reaparse points (like FAT32) then do not even try to create reparse point. Same applies for older Samba servers on Linux which do not support reparse point at all. On Wednesday 29 January 2025 17:39:24 Steve French wrote: > In the patch below, do you have an example you tried where server > without reparse point support that left a file/directory around after > a failed attempt to create FIFO/SYMLINK or other special file via > reparse point? > > [PATCH 18/62] cifs: Check if server supports reparse points before using them > > Do not attempt to query or create reparse point when server fs does not > support it. This will prevent creating unusable empty object on the server. > > -- > Thanks, > > Steve
