From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Samba strict allocate = yes stops btrfs compression working
Date: Fri, 23 Aug 2013 09:08:21 +0000 (UTC) [thread overview]
Message-ID: <pan$e0fe5$102b89f1$6420a15b$7c2eaf18@cox.net> (raw)
In-Reply-To: CE3CD861.3C3F5%mark@backupsystems. co.uk
Mark Ridley posted on Fri, 23 Aug 2013 09:20:04 +0100 as excerpted:
> I don't want to try nodatacow (which would probably fix the issue), but
> you lose compression on the whole filesystem, autodefrag doesn't fix it
> either.
I don't do servantware (in the context of my sig) and thus don't do samba
here, so I'll just black-box that side of things entirely.
But from the btrfs side, are you considering nodatacow at the filesystem
or individual file level? It seems doing it at the individual file level
might be what you need.
Note that nodatacow must be set on the file at creation in ordered to
work, which is impractical to do directly. However, if you can arrange
for the files in question to appear in a particular directory, you can
set the nodatacow attribute on the directory, and files created within it
will inherit that.
It seems to me that should do what you need, PROVIDED that you can
arrange for the files to appear in a particular dir/dir-tree, not more or
less randomly written throughout the entire (btrfs) filesystem.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-08-23 9:08 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
[not found] ` <CE3CD861.3C3F5%mark@backupsystems. co.uk>
2013-08-23 9:08 ` Duncan [this message]
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='pan$e0fe5$102b89f1$6420a15b$7c2eaf18@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).