From ecf48af135e4c1ebc5aafe4b3dad785162f5949a Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Wed, 15 Dec 2010 13:32:09 -0800 Subject: Change strict allocate to default to true. (cherry picked from commit 820ea22a07b062b1717d35de8fa7051fc1067c3f) --- docs-xml/smbdotconf/tuning/strictallocate.xml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs-xml/smbdotconf/tuning/strictallocate.xml') diff --git a/docs-xml/smbdotconf/tuning/strictallocate.xml b/docs-xml/smbdotconf/tuning/strictallocate.xml index 1855574776..9311eb6b80 100644 --- a/docs-xml/smbdotconf/tuning/strictallocate.xml +++ b/docs-xml/smbdotconf/tuning/strictallocate.xml @@ -10,9 +10,10 @@ of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size. In UNIX terminology this means that Samba will stop creating sparse files. - This can be slow on some systems. When you work with large files like - >100MB or so you may even run into problems with clients running into - timeouts. + Modern UNIX filesystems now support extents and so in Samba 3.6.0 we + have changed this parameter to default to "yes". On older filesystems + without extents you might want to turn this parameter to "no". + When you have an extent based filesystem it's likely that we can make use of unwritten extents which allows Samba to allocate even large amounts @@ -28,9 +29,9 @@ preallocation is probably an expensive operation where you will see reduced performance and risk to let clients run into timeouts when creating large files. Examples are ext3, ZFS, HFS+ and most others, so be aware if you - activate this setting on those filesystems. + leave the default setting on those filesystems. -no +yes -- cgit