----- Ursprüngliche Mail ----- > Von: "bfields" <bfields@xxxxxxxxxxxx> >> Unless I badly misunderstood the code it comes from fs/nfs/client.c's >> nfs_create_server() where the NFS client fetches NFS_ATTR_FATTR via getattr(). >> So it should be unique: >> https://datatracker.ietf.org/doc/html/rfc7530#section-5.8.1.9 > > Unique within one server, but not across different servers. > > Depending on how your servers assign fsids, collisions might be quite > likely. Results of a collision would be pretty bad. Hmm. So this means when you have a setup where the same file system is exported via multiple servers (the load balancing use case), getattr on the same file can report a different fsid at any time? This renders the fsid attribute close to useless :-( Anyway, this is not a show stopper just makes more clear that we should take the FSID_NUM mapping path. Please stay tuned, I'll send ASAP another patch. Thanks, //richard
