From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Samba strict allocate = yes stops btrfs compression working
Date: Fri, 23 Aug 2013 12:35:25 -0700 [thread overview]
Message-ID: <kv8dhn$lko$1@ger.gmane.org> (raw)
In-Reply-To: <CE3CD861.3C3F5%mark@backupsystems.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23/08/13 01:20, Mark Ridley wrote:
> The main reason I started using strict allocate = yes on samba was out
> of desperation/exasperation with BTRFS.
The most effective performance option is to turn oplocks on.
Opportunistic locks are granted to a client when it is the only one with a
file open. That lets it do caching and not even tell the server about
record locking. Once another client opens the same file then the first
client has to flush all outstanding writes, its caches, record locking etc.
I don't know what Samba currently uses as the default value, but it is
traditionally set to off because there are scenarios under which it isn't
sufficiently robust (eg access on the Unix server side, a network break
when there is outstanding data).
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/locking.html#id2616903
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIXuX0ACgkQmOOfHg372QSRwgCgwwwoo7QqRql8+CS5xggRBVRt
krAAn1wFiIIliZJ7WbWh/oh8crEWLgfR
=HZG9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-08-23 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 9:57 Samba strict allocate = yes stops btrfs compression working Mark Ridley
2013-08-22 14:07 ` Josef Bacik
2013-08-22 18:29 ` Kai Krakow
2013-08-22 18:47 ` Josef Bacik
2013-08-23 9:03 ` Mark Ridley
2013-08-23 8:01 ` Roger Binns
2013-08-23 8:20 ` Mark Ridley
2013-08-23 19:35 ` Roger Binns [this message]
[not found] ` <CE3CD861.3C3F5%mark@backupsystems. co.uk>
2013-08-23 9:08 ` Duncan
2013-08-23 9:14 ` Mark Ridley
2013-08-23 13:43 ` Clemens Eisserer
2013-08-23 9:09 ` Mark Ridley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='kv8dhn$lko$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).