rdiff-backup-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Rdiff-backup-commits] rdiff-backup FAQ-body.html


From: Andrew Ferguson
Subject: [Rdiff-backup-commits] rdiff-backup FAQ-body.html
Date: Sun, 05 Oct 2008 17:39:18 +0000

CVSROOT:        /sources/rdiff-backup
Module name:    rdiff-backup
Changes by:     Andrew Ferguson <owsla> 08/10/05 17:39:18

Modified files:
        .              : FAQ-body.html 

Log message:
        more FAQ updates for CIFS issues

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/rdiff-backup/FAQ-body.html?cvsroot=rdiff-backup&r1=1.23&r2=1.24

Patches:
Index: FAQ-body.html
===================================================================
RCS file: /sources/rdiff-backup/rdiff-backup/FAQ-body.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- FAQ-body.html       4 Oct 2008 04:08:57 -0000       1.23
+++ FAQ-body.html       5 Oct 2008 17:39:18 -0000       1.24
@@ -135,9 +135,11 @@
        the CIFS mount. At least one user has reported success when using this
        option while mounting a NAS system via CIFS. See the mount.cifs man page
        for more information.<br><br></li>
-       <li>Other CIFS mount options which may be helpful include 
<code>nocase</code>
-       and <code>directio</code>. A user with a DroboShare reported that 
-       <code>-o mapchars,nocase,directio</code> worked for that NAS 
appliance.</li>
+       <li>Other CIFS mount options which may be helpful include 
<code>nocase</code>,
+       <code>directio</code>, and <code>sfu</code>. Also, try changing the 
value of
+       <code>/proc/fs/cifs/LinuxExtensionsEnabled</code> (requires remount). A 
user
+       with a DroboShare reported that <code>-o mapchars,nocase,directio</code>
+       worked for that NAS appliance.</li>
 </ul>
 <p>If you're still having trouble backing up to a CIFS or smbfs mount, try 
searching the
 <a href="http://lists.gnu.org/archive/html/rdiff-backup-users/";>mailing-list 
archives</a> and then sending




reply via email to

[Prev in Thread] Current Thread [Next in Thread]