diff options
Diffstat (limited to 'docs-xml/smbdotconf/misc')
| -rw-r--r-- | docs-xml/smbdotconf/misc/ctdblocktimewarnthreshold.xml | 26 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/misc/logwriteablefilesonexit.xml | 15 |
2 files changed, 30 insertions, 11 deletions
diff --git a/docs-xml/smbdotconf/misc/ctdblocktimewarnthreshold.xml b/docs-xml/smbdotconf/misc/ctdblocktimewarnthreshold.xml index 149d8d67e3..a3289a93bc 100644 --- a/docs-xml/smbdotconf/misc/ctdblocktimewarnthreshold.xml +++ b/docs-xml/smbdotconf/misc/ctdblocktimewarnthreshold.xml @@ -4,13 +4,25 @@ advanced="1" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> - <para>In a cluster, ctdb is very unhappy if tdb database locks - are held for extended periods of time. This parameter adds a - warning threshold in milliseconds. If Samba holds a lock for - longer that ctdb locktime warn threshold milliseconds, a debug - level 0 message is printed when the lock is released. This is - mainly a debugging aid for post-mortem analysis.</para> - <para>If this parameter is set to 0, no message is printed.</para> + + <para> + In a cluster environment using Samba and ctdb it is critical + that locks on central ctdb-hosted databases like locking.tdb + are not held for long. With the current Samba architecture + it happens that Samba takes a lock and while holding that + lock makes file system calls into the shared cluster file + system. This option makes Samba warn if it detects that it + has held locks for the specified number of milliseconds. If + this happens, <emphasis>smbd</emphasis> will emit a debug level 0 + message into its logs and potentially into syslog. The most likely + reason for such a log message is that an operation of the cluster + file system Samba exports is taking longer than expected. + The messages are meant as a debugging aid for potential + cluster problems. + </para> + + <para>The default value of 0 disables this logging.</para> + </description> <value type="default">0</value> </samba:parameter> diff --git a/docs-xml/smbdotconf/misc/logwriteablefilesonexit.xml b/docs-xml/smbdotconf/misc/logwriteablefilesonexit.xml index 1c75457803..9d2b750943 100644 --- a/docs-xml/smbdotconf/misc/logwriteablefilesonexit.xml +++ b/docs-xml/smbdotconf/misc/logwriteablefilesonexit.xml @@ -5,10 +5,17 @@ xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> <para> - This boolean option controls whether at exit time the server - dumps a list of files with debug level 0 that were still open - for write. This is an administrative aid to find the files - that were potentially corrupt if the network connection died. + When the network connection between a CIFS client and Samba + dies, Samba has no option but to simply shut down the server + side of the network connection. If this happens, there is a + risk of data corruption because the Windows client did not + complete all write operations that the Windows application + requested. Setting this option to "yes" makes smbd log with + a level 0 message a list of all files that have been opened + for writing when the network connection died. Those are the + files that are potentially corrupted. It is meant as an aid + for the administrator to give him a list of files to do + consistency checks on. </para> </description> |