admin-guide/cifs/usage.rst

6 as older dialects, originally called "CIFS" or SMB1).
8 The CIFS VFS module for Linux supports many advanced network filesystem
10 It was designed to comply with the SNIA CIFS Technical Reference (which
14 Information Foundation.  CIFS and now SMB3 has now become a defacto
46 If you have built the CIFS vfs as module (successfully) simply
50 If you have built the CIFS vfs into the kernel itself, follow the instructions
55 the CIFS VFS web site) copy it to the same directory in which mount helpers
79 on mount (or vers=2.0 for Windows Vista).  Note that the CIFS (vers=1.0) is
140 but there are useful protocol extensions for the older less secure CIFS
142 (CIFS/SMB1), we recommend using a server that supports the SNIA CIFS
144 2.2.5 or later) but the CIFS vfs works fine with a wide variety of CIFS servers.
146 not have a server that supports the Unix extensions for CIFS (such as Samba
147 2.2.5 or later).  To enable the Unix CIFS Extensions in the Samba server, add
168 The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers
170 then POSIX support in the CIFS configuration options when building the cifs
177 which may not be what you want, although if the CIFS Unix extensions are
185 Note that Samba 2.2.7 or later includes a fix that allows the CIFS VFS to delete
199 later, but only for remote clients using the CIFS Unix extensions, and will
206 Once the CIFS VFS support is built into the kernel or installed as a module
229 Although mounting using format corresponding to the CIFS URL specification is
255 Servers must support either "pure-TCP" (port 445 TCP/IP CIFS connections) or RFC
266 would be forbidden for Windows/CIFS semantics) as long as the server is
269 ``mapposix`` can be used on CIFS (vers=1.0) to force the mapping of
274 CIFS VFS Mount Options
280 		the CIFS session.
291 		Set the SMB/CIFS workgroup name prepended to the
292 		username during CIFS session establishment
296 		which do support the CIFS Unix extensions, such as a
305 		For servers which do not support the CIFS Unix
337 		If CIFS Unix extensions are not supported by the server
349 		disk caching is functional for CIFS files opened as read-only.
351 		If CIFS Unix extensions are not supported by the server
379 		maximum wsize currently allowed by CIFS is 57344 (fourteen
417 		to servers such as Samba which support the CIFS Unix Extensions.
454 		supports the CIFS Unix Extensions but the UIDs/GIDs on the
457 		non CIFS Unix Extension mounts for cases in which the default
474 		or the CIFS Unix Extensions equivalent and for those
486 		If the CIFS Unix extensions are negotiated with the server
489 		devices (create, mkdir, mknod).  If the CIFS Unix Extensions
501 		the client) set the uid and gid is the default. If the CIFS
549 		allows the CIFS client to recognize files created with
563 		If CIFS Unix extensions are supported, attempt to
565 		characters forbidden in typical CIFS filenames, without
568 		If CIFS Unix extensions are supported, do not request
572 		Disable the CIFS Unix Extensions for this mount (tree
628 		When the CIFS Unix Extensions are not negotiated, attempt to
640 		the server supports the CIFS Unix Extensions.
654 		check to see whether a file is cacheable.  CIFS has no way
712 DebugData		Displays information about active CIFS sessions and
774 			use the CIFS "UNIX" extensions which are optional
775 			protocol enhancements that allow CIFS servers
778 			such as Samba that support the CIFS Unix
842 CIFS kernel module parameters