diff options
| author | Steve French <smfrench@gmail.com> | 2014-08-12 06:05:25 +0400 |
|---|---|---|
| committer | Steve French <smfrench@gmail.com> | 2014-08-13 22:18:35 +0400 |
| commit | 3d1a3745d8ca7ccdf00905b01fd5ab42ff523a94 (patch) | |
| tree | 17ba01e56cbf7238e5ce59967f1e073da95b885b /fs/cifs/link.c | |
| parent | 8ae31240ccc8ff339101e2d023b82cb7c93dd002 (diff) | |
| download | linux-3d1a3745d8ca7ccdf00905b01fd5ab42ff523a94.tar.xz | |
Add sparse file support to SMB2/SMB3 mounts
Many Linux filesystes make a file "sparse" when extending
a file with ftruncate. This does work for CIFS to Samba
(only) but not for SMB2/SMB3 (to Samba or Windows) since
there is a "set sparse" fsctl which is supposed to be
sent to mark a file as sparse.
This patch marks a file as sparse by sending this simple
set sparse fsctl if it is extended more than 2 pages.
It has been tested to Windows 8.1, Samba and various
SMB2/SMB3 servers which do support setting sparse (and
MacOS which does not appear to support the fsctl yet).
If a server share does not support setting a file
as sparse, then we do not retry setting sparse on that
share.
The disk space savings for sparse files can be quite
large (even more significant on Windows servers than Samba).
Signed-off-by: Steve French <smfrench@gmail.com>
Reviewed-by: Shirish Pargaonkar <spargaonkar@suse.com>
Diffstat (limited to 'fs/cifs/link.c')
0 files changed, 0 insertions, 0 deletions