From: Sachin Prabhu Date: Thu, 15 Oct 2020 11:14:33 +0000 (+0100) Subject: docs-xml/manpages: Add warning about write-behind translator for vfs_glusterfs X-Git-Tag: samba-4.12.10~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0004099938068db5c81628a6a2b077807218dd86;p=thirdparty%2Fsamba.git docs-xml/manpages: Add warning about write-behind translator for vfs_glusterfs Add warning about data corruption with the write-behind translator. The data corruption is highlighted by the smbtorture test smb2.rw.rw1. More information about this data corruption issue is available in the bz. BUG: https://bugzilla.samba.org/show_bug.cgi?id=14486 Signed-off-by: Sachin Prabhu Reviewed-by: Jeremy Allison Reviewed-by: Guenther Deschner (cherry picked from commit 08f8f665d409ee7b93840c25a8142f2ce8bacfa1) --- diff --git a/docs-xml/manpages/vfs_glusterfs.8.xml b/docs-xml/manpages/vfs_glusterfs.8.xml index cf3b8e5e384..7a4da1af919 100644 --- a/docs-xml/manpages/vfs_glusterfs.8.xml +++ b/docs-xml/manpages/vfs_glusterfs.8.xml @@ -161,6 +161,28 @@ + + CAVEATS + + + The GlusterFS write-behind performance translator, when used + with Samba, could be a source of data corruption. The + translator, while processing a write call, immediately returns + success but continues writing the data to the server in the + background. This can cause data corruption when two clients + relying on Samba to provide data consistency are operating on + the same file. + + + The write-behind translator is enabled by default on GlusterFS. + The vfs_glusterfs plugin will check for the presence of the + translator and refuse to connect if detected. + Please disable the write-behind translator for the GlusterFS + volume to allow the plugin to connect to the volume. + + + + VERSION