From 29a84670a9fa1fa461e669ac61c35cb3d03c362a Mon Sep 17 00:00:00 2001 From: Suresh Jayaraman Date: Wed, 23 Dec 2009 11:41:39 -0500 Subject: [PATCH] doc: update mount.cifs man page with nounix option Change since last post: - fix build error due to superfluous tag. - ensure it builds fine. Also add a section on INODE NUMBERS that discusses inode numbers more thoroughly and add reference to it in "nounix" and "noserverino" options. Thanks to Jeff Layton for explaining those details. Signed-off-by: Suresh Jayaraman Signed-off-by: Jeff Layton --- docs-xml/manpages-3/mount.cifs.8.xml | 54 ++++++++++++++++++++++++++++++++++-- 1 file changed, 52 insertions(+), 2 deletions(-) diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml index 372b4772f13..d930600437e 100644 --- a/docs-xml/manpages-3/mount.cifs.8.xml +++ b/docs-xml/manpages-3/mount.cifs.8.xml @@ -477,12 +477,35 @@ permissions in memory that can't be stored on the server. This information can d noserverino - client generates inode numbers (rather than using the actual one - from the server) by default. + + + Client generates inode numbers (rather than + using the actual one from the server) by default. + + + See section INODE NUMBERS for + more information. + nounix + + + Disable the CIFS Unix Extensions for this mount. This + can be useful in order to turn off multiple settings at once. + This includes POSIX acls, POSIX locks, POSIX paths, symlink + support and retrieving uids/gids/mode from the server. This + can also be useful to work around a bug in a server that + supports Unix Extensions. + + + See section INODE NUMBERS for + more information. + + + + nouser_xattr (default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. @@ -533,6 +556,33 @@ permissions in memory that can't be stored on the server. This information can d + INODE NUMBERS + + When Unix Extensions are enabled, we use the actual inode + number provided by the server in response to the POSIX calls as an + inode number. + + + When Unix Extensions are disabled and "serverino" mount option + is enabled there is no way to get the server inode number. The + client typically maps the server-assigned "UniqueID" onto an inode + number. + + + Note that the UniqueID is a different value from the server + inode number. The UniqueID value is unique over the scope of the entire + server and is often greater than 2 power 32. This value often makes + programs that are not compiled with LFS (Large File Support), to + trigger a glibc EOVERFLOW error as this won't fit in the target + structure field. It is strongly recommended to compile your programs + with LFS support (i.e. with -D_FILE_OFFSET_BITS=64) to prevent this + problem. You can also use "noserverino" mount option to generate inode + numbers smaller than 2 power 32 on the client. But you may not be able + to detect hardlinks properly. + + + + FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS The core CIFS protocol does not provide unix ownership -- 2.11.4.GIT