Patchwork doc: add information about nounix mount option (try#2)

login
register
mail settings
Submitter Suresh Jayaraman
Date Dec. 21, 2009, 9:19 a.m.
Message ID <1261387178-8348-1-git-send-email-sjayaraman@suse.de>
Download mbox | patch
Permalink /patch/41539/
State New
Headers show

Comments

Suresh Jayaraman - Dec. 21, 2009, 9:19 a.m.
Also add a section on INODE NUMBERS that discusses inode numbers more
thoroughly and add reference to it in "nounix" and "noserverino" options.

Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de>
---
 docs-xml/manpages-3/mount.cifs.8.xml |   47 ++++++++++++++++++++++++++++++++-
 1 files changed, 45 insertions(+), 2 deletions(-)
Jeff Layton - Dec. 21, 2009, 12:14 p.m.
On Mon, 21 Dec 2009 14:49:38 +0530
Suresh Jayaraman <sjayaraman@suse.de> wrote:

> Also add a section on INODE NUMBERS that discusses inode numbers more
> thoroughly and add reference to it in "nounix" and "noserverino" options.
> 
> Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de>
> ---
>  docs-xml/manpages-3/mount.cifs.8.xml |   47 ++++++++++++++++++++++++++++++++-
>  1 files changed, 45 insertions(+), 2 deletions(-)
> 
> diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml
> index 372b477..cf9b6a5 100644
> --- a/docs-xml/manpages-3/mount.cifs.8.xml
> +++ b/docs-xml/manpages-3/mount.cifs.8.xml
> @@ -477,12 +477,36 @@ permissions in memory that can't be stored on the server. This information can d
>  
>          <varlistentry>
>                  <term>noserverino</term>
> -                <listitem><para>client generates inode numbers (rather than using the actual one
> -                from the server) by default.
> +		<listitem>
> +		<para>
> +			Client generates inode numbers (rather than
> +		using the actual one from the server) by default.
> +		</para>
> +		<para>
> +			See section <emphasis>INODE NUMBERS</emphasis> for
> +		more information.
> +		</para>
>  		</para></listitem>
>          </varlistentry>
>  
>          <varlistentry>
> +		<term>nounix</term>
> +		<listitem>
> +		<para>
> +			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.
> +		</para>
> +		<para>
> +		See section <emphasis>INODE NUMBERS</emphasis> for
> +		more information.
> +		</para> </listitem>
> +        </varlistentry>
> +
> +        <varlistentry>
>                  <term>nouser_xattr</term>
>                  <listitem><para>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </para></listitem>
>          </varlistentry>
> @@ -533,6 +557,25 @@ permissions in memory that can't be stored on the server. This information can d
>  </refsect1>
>  
>  <refsect1>
> +	<title>INODE NUMBERS</title>
> +	<para>
> +		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.
> +	</para>
> +	<para>
> +		When Unix Extensions are disabled and "serverino" mount option
> +	is enabled there is no way to get the server inode number. So a
> +	"UniqueID" from the server is used, instead. A UniqueID is different
> +	from a inode number and it is unique over the scope of the entire
> +	server. It is often greater than 2 power 32. To avoid using this huge
> +	UniqueID's make sure you build your programs with LFS support. 

This sentence doesn't make much sense. If you build the programs with
LFS support you'll still be using the unique ID as an inode number. The
problems with large inode numbers and non-LFS programs probably need to
be explained more thoroughly here so that people understand why
building with LFS support is important.

Other than that, the manpage update looks good.

> You can
> +	also use "noserverino" mount option to overcome this, but you may not
> +	be able to detect hardlinks properly.
> +	</para>
> +</refsect1>
> +
> +<refsect1>
>  	<title>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</title>
>  
>  	<para> The core CIFS protocol does not provide unix ownership
> _______________________________________________
> linux-cifs-client mailing list
> linux-cifs-client@lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux-cifs-client
>

Patch

diff --git a/docs-xml/manpages-3/mount.cifs.8.xml b/docs-xml/manpages-3/mount.cifs.8.xml
index 372b477..cf9b6a5 100644
--- a/docs-xml/manpages-3/mount.cifs.8.xml
+++ b/docs-xml/manpages-3/mount.cifs.8.xml
@@ -477,12 +477,36 @@  permissions in memory that can't be stored on the server. This information can d
 
         <varlistentry>
                 <term>noserverino</term>
-                <listitem><para>client generates inode numbers (rather than using the actual one
-                from the server) by default.
+		<listitem>
+		<para>
+			Client generates inode numbers (rather than
+		using the actual one from the server) by default.
+		</para>
+		<para>
+			See section <emphasis>INODE NUMBERS</emphasis> for
+		more information.
+		</para>
 		</para></listitem>
         </varlistentry>
 
         <varlistentry>
+		<term>nounix</term>
+		<listitem>
+		<para>
+			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.
+		</para>
+		<para>
+		See section <emphasis>INODE NUMBERS</emphasis> for
+		more information.
+		</para> </listitem>
+        </varlistentry>
+
+        <varlistentry>
                 <term>nouser_xattr</term>
                 <listitem><para>(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise. </para></listitem>
         </varlistentry>
@@ -533,6 +557,25 @@  permissions in memory that can't be stored on the server. This information can d
 </refsect1>
 
 <refsect1>
+	<title>INODE NUMBERS</title>
+	<para>
+		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.
+	</para>
+	<para>
+		When Unix Extensions are disabled and "serverino" mount option
+	is enabled there is no way to get the server inode number. So a
+	"UniqueID" from the server is used, instead. A UniqueID is different
+	from a inode number and it is unique over the scope of the entire
+	server. It is often greater than 2 power 32. To avoid using this huge
+	UniqueID's make sure you build your programs with LFS support. You can
+	also use "noserverino" mount option to overcome this, but you may not
+	be able to detect hardlinks properly.
+	</para>
+</refsect1>
+
+<refsect1>
 	<title>FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS</title>
 
 	<para> The core CIFS protocol does not provide unix ownership