-----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----- -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
