[linux-cifs-client] lstat reporting different inode numbers on smb than it does on other filesystems

[Hein-Pieter van Braam]

Hi steve!

I would love to take al look at that patch! in our envionment this isn't an 
issue anyway. I myself was thinking about maybe when passing this 
information, ceck weither or not a file is a link, and if it is, set the ino 
the same as the target?
I think that would fix inode collisions, I am not very sure if this is 
feasable though, and it might bog down the speed of stat... 

I think the best way to implement this would be with a mount parm, as you will 
very probably *only* need this baviour if you use the share as a home 
directory. (at least, I haven't found any other way to trigger an error based 
on this behaviour)

greeting!

Hein-Pieter van Braam


On Tuesday 02 November 2004 19:10, you wrote:
> > on ext2/3 and friends, the inod numbers in an lstat are the same for
>
> both the
>
> >source and the destination of a hardlink, on cifs, it gets its own inode
> >number, that is then passed.
>
> I can use the inode number from the server, but I risk inode number
> collisions if the server exports two mounted filesystems under the same
> share.
>
> If you would like I can send you a patch to use the server's inode number,
> but it would probably be best to make that optional (a mount parm or
> /proc/fs/cifs config file).
>
>
>
> Steve French
> Senior Software Engineer
> Linux Technology Center - IBM Austin
> phone: 512-838-2294
> email: sfrench at-sign us dot ibm dot com