From: Mark Ridley <mark@backupsystems.co.uk>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Samba strict allocate = yes stops btrfs compression working
Date: Fri, 23 Aug 2013 10:03:22 +0100 [thread overview]
Message-ID: <CE3CE3BC.3C431%mark@backupsystems.co.uk> (raw)
In-Reply-To: <6t1iea-qg7.ln1@hurikhan77.spdns.de>
I tried defrag -c and it does nothing to files that have come in with
strict allocate = yes.
On 22/08/2013 19:29, "Kai Krakow" <hurikhan77+btrfs@gmail.com> wrote:
>Josef Bacik <jbacik@fusionio.com> schrieb:
>
>> 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,
>
>Good to know, this renders btrfs as efficient storage backend for Windows
>file shares pretty useless. Does this also happen with compress-force?
>
>As a work-around one could write a cronjob that regularly defrags all
>files
>changed since the last run with -c option...
>
>Thanks,
>Kai
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-23 9:03 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 [this message]
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=CE3CE3BC.3C431%mark@backupsystems.co.uk \
--to=mark@backupsystems.co.uk \
--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).