I would expect when the inode collision is noted that "cifs_autodisable_serverino()" will get called in the Linux client and you should see: "Autodisabling the user of server inode numbers on ..." "Consider mounting with noserverino to silence this message" If this is easy to setup we could try some tricks when we encounter such a reparse point - do you have patch ideas for the client to fake up inode numbers in this case? On Wed, Mar 1, 2023 at 7:39 PM Andrew Walker <awalker@xxxxxxxxxxxxx> wrote: > > On Wed, Mar 1, 2023 at 5:37 PM Paulo Alcantara <pc@xxxxxxxxxxxxx> wrote: > > > > Andrew Walker <awalker@xxxxxxxxxxxxx> writes: > > > > > On my Windows server I mounted multiple NTFS volumes within the same > > > share and played around until I was able to create directories with > > > the same fileid number. > > > > Did you try it with 'noserverino' mount option? For more information, > > see mount.cifs(8). > > Yes. In this case I get a unique inode number > > > Did it work with older kernels? > I only tested with 5.15 kernel. Was there a different algorithm in > older kernels that's worth testing? > > > Perhaps we could conditionally stop trusting file ids sent by the server > > as we currently do for hardlinks when we see these reparse points as > > well. > > Maybe fail chdir with EXDEV unless mount is with noserverino? -- Thanks, Steve
