diff options
| author | Björn Jacke <bj@sernet.de> | 2009-12-02 15:13:37 +0100 |
|---|---|---|
| committer | Björn Jacke <bj@sernet.de> | 2009-12-02 21:21:43 +0100 |
| commit | 95c18626107484d5d1d475e34fc4dde03cfe6ff5 (patch) | |
| tree | 508651f48665b308ec49ef600f7b58de0916c2a2 /source3/modules/vfs_shadow_copy.c | |
| parent | 486c8d57ec5a9aa63aff275621ff45c22b8cde61 (diff) | |
| download | samba-95c18626107484d5d1d475e34fc4dde03cfe6ff5.tar.gz samba-95c18626107484d5d1d475e34fc4dde03cfe6ff5.tar.bz2 samba-95c18626107484d5d1d475e34fc4dde03cfe6ff5.zip | |
s3: prefer posix_fallocate for doing "strict allocate"
posix_fallocate is more efficient than manual zero'ing the file. When
preallocation in kernel space is supported it's extremely fast. Support for
preallocation at fs layer via posix_fallocate and fallocate at kernel site
can be found in Linux kernel 2.6.23/glibc 2.10 with ext4, XFS and OCFS2. Other
systems that I know of which support fast preallocation in kernel space are
AIX 6.1 with JFS2 and recent Solaris versions with ZFS maybe UFS2, too.
People who have a system with preallocation in kernel space might want to set
"strict allocate = yes". This reduces file fragentation and it's also safer for
setups with quota being turned on.
As of today most systems still don't have preallocation in kernel space, and
that's why "strict allocate = no" will stay the default for now.
Diffstat (limited to 'source3/modules/vfs_shadow_copy.c')
0 files changed, 0 insertions, 0 deletions