From: Josef Bacik <jbacik@fusionio.com>
To: Mark Ridley <mark@backupsystems.co.uk>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Samba strict allocate = yes stops btrfs compression working
Date: Thu, 22 Aug 2013 10:07:52 -0400 [thread overview]
Message-ID: <20130822140752.GO3990@localhost.localdomain> (raw)
In-Reply-To: <loom.20130822T115349-248@post.gmane.org>
On Thu, Aug 22, 2013 at 09:57:24AM +0000, Mark Ridley wrote:
> Hi,
>
> If i set strict allocate = yes in samba to speed up the transfer
> of a mssql database dump,
> then btrfs does not compress the file.
> I have tried it also by just copying a small file in Windows to the
> samba share and the same.
> I have tried btrfs mount options autodefrag and then
> btrfs fi defrag -c and the file still does not get compressed.
>
> I have tried kernels 3.6.11, 3.8 and 3.10.7 on FC16 and FC18.
>
> Any help, much appreciated.
>
Not sure what strict allocate = yes does, but I assume it probably does
fallocate() in which case yeah we aren't going to compress, we'll just write
into the preallocated space. We don't support compressed writes into
preallocated space ATM, and I'm not sure we ever will. Thanks,
Josef
next prev parent reply other threads:[~2013-08-22 14:07 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 [this message]
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
[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=20130822140752.GO3990@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@backupsystems.co.uk \
/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).