From: Chris Mason <chris.mason@oracle.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: Lee Trager <lt73@cs.drexel.edu>,
linux-btrfs@vger.kernel.org, balajirrao@gmail.com,
miguel.filipe@gmail.com
Subject: Re: Compressed Filesystem
Date: Tue, 28 Oct 2008 13:46:21 -0400 [thread overview]
Message-ID: <1225215981.6448.178.camel@think.oraclecorp.com> (raw)
In-Reply-To: <49074EA3.2080801@oracle.com>
On Tue, 2008-10-28 at 10:40 -0700, Zach Brown wrote:
> > Compression is optional and off by default (mount -o compress to enable
> > it). When enabled, every file is compressed.
>
> Compression is attempted as files are written when the mount option is
> enabled, right?
Yes, and if the compression doesn't make a given set of pages smaller it
quickly backs off and goes back to writing it straight through.
>
> There isn't a background scrubber that tries to compress files which are
> already written?
No, but if you mount with compression on and use the single file defrag
ioctl (btrfsctl -d some_file) it'll compress it.
-chris
next prev parent reply other threads:[~2008-10-28 17:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:54 Compressed Filesystem Lee Trager
2008-10-28 15:47 ` Chris Mason
2008-10-28 16:33 ` Lee Trager
2008-10-28 17:38 ` Chris Mason
2008-10-28 17:40 ` Zach Brown
2008-10-28 17:46 ` Chris Mason [this message]
[not found] ` <53696.2001:470:e828:1::2:2.1225304096.squirrel@avalon.arbitraryconstant.com>
2008-10-29 20:08 ` Chris Mason
2008-11-04 0:08 ` Chris Samuel
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 22:14 devzero
2008-12-15 23:07 ` Lee Trager
2008-12-15 23:19 devzero
2008-12-16 15:20 ` Lee Trager
2008-12-16 15:26 ` Chris Mason
2008-12-16 16:25 ` Lee Trager
2008-12-16 19:45 ` Roland
2008-12-18 15:55 ` Chris Mason
2008-12-16 18:14 devzero
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=1225215981.6448.178.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=balajirrao@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
--cc=miguel.filipe@gmail.com \
--cc=zach.brown@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.