On Tue, 17 May 2011 23:54:27 +0400 Pavel Shilovsky <[email protected]> wrote:
> In mount.cifs.8 page we have: "Client generates inode numbers (rather > than using the actual one from the server) by default", but if we look > at the code we can see that > we use server's numbers by default instead: > > http://git.kernel.org/?p=linux/kernel/git/sfrench/cifs-2.6.git;a=blob;f=fs/cifs/connect.c;h=277262a8e82f282d4a32b0ddd4a244bc55e99472;hb=221d1d797202984cb874e3ed9f1388593d34ee22#l859 > > So, where is a error? > I'm not sure it's an error per-se, but the manpage is unclear and poorly-worded: noserverino Client generates inode numbers (rather than using the actual one from the server) by default. I think that the intent was to say that when noserverino is used, it generates it generates inode numbers by default. That makes it sounds though like it may use server inode numbers in some cases which is of course incorrect. The default is to use server inode numbers (or uniqueid's) if they are available and can reliably be used on the client (i.e. aren't autodisabled). Care to propose a patch to clarify the manpage? -- Jeff Layton <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
