From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: C Anthony Risinger <anthony@extof.me>
Cc: Felix Blanke <felixblanke@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates
Date: Tue, 18 Jan 2011 11:56:37 -0600 [thread overview]
Message-ID: <AANLkTimcLOFoJ8m2PBG9nsfw4L3FGPNa+RN=Cj_-nZdC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimDGtzw9GSC7FigFsKO+w9cO30LUZ2=XK0aK9Hj@mail.gmail.com>
On Tue, Jan 18, 2011 at 9:22 AM, C Anthony Risinger <anthony@extof.me> wrote:
> On Tue, Jan 18, 2011 at 4:14 AM, Felix Blanke <felixblanke@gmail.com> wrote:
>> Hi,
>>
>> just slap me if the question is stupid, but when will all those new features be added
>> to the btrfs-progs?
>>
>> The last commit is at
>> "git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git"
>> is from oct. 2010?!?
>
> i don't know about the readonly snapshots, but the LZO stuff is a
> mount option; should be in the pull.
>
> and for the record, i'm totally stoked to run LZO on all my btrfs
> machines (esp. the netbooks/SSDs :-)
>
> C Anthony
There was also a patch submitted by Li Zefan for LZO support in btrfs-progs:
http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg06931.html
If I recall correctly, btrfs-progs will throw out an error once you
use LZO compression since btrfs-progs needs to be made aware of the
INCOMPAT flag in the patch submitted above.
My local btrfs-progs git repository also incorporates patches to
support mixed data+metadata (which also uses an INCOMPAT flag aleady
in the kernel code) and for the filesystem diskinfo command.
A quick search for "btrfs-progs" in my Mailing List archive turns up a
number of other btrfs-progs patch proposals since October.
next prev parent reply other threads:[~2011-01-18 17:56 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:13 [GIT PULL] Btrfs updates Chris Mason
2011-01-18 10:14 ` Felix Blanke
2011-01-18 15:22 ` C Anthony Risinger
2011-01-18 17:56 ` Mitch Harder [this message]
2011-01-18 18:51 ` C Anthony Risinger
2011-01-19 9:15 ` Spelic
2011-01-22 23:41 ` Clemens Eisserer
2011-01-22 23:53 ` cwillu
2011-01-18 18:55 ` Goffredo Baroncelli
2011-03-09 22:01 ` Diego Calleja
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 14:30 Chris Mason
2013-03-29 17:47 Chris Mason
2013-03-09 0:38 Chris Mason
2013-02-16 1:55 Chris Mason
2012-12-17 21:44 Chris Mason
2012-12-19 18:09 ` Roy Sigurd Karlsbakk
2012-12-19 19:07 ` Hugo Mills
2012-12-17 21:28 Chris Mason
2012-08-29 16:01 Chris Mason
2012-07-05 19:55 Chris Mason
2012-06-21 15:47 Chris Mason
2012-06-15 18:09 Chris Mason
2012-06-15 23:57 ` Linus Torvalds
2012-06-16 0:21 ` Chris Mason
2012-06-01 13:18 Chris Mason
2012-04-13 13:38 Chris Mason
2012-04-16 1:19 ` Tsutomu Itoh
2012-03-10 2:01 Chris Mason
2012-02-24 16:41 Chris Mason
2011-12-01 15:39 Chris Mason
2011-12-05 8:10 ` Miao Xie
2011-12-05 13:14 ` Chris Mason
2011-12-05 14:08 ` David Sterba
2011-12-06 3:25 ` Miao Xie
2011-08-18 18:04 Chris Mason
2011-08-18 21:51 ` Sage Weil
2011-08-20 14:01 ` Chris Mason
2011-07-27 22:46 Chris Mason
2011-06-27 18:15 Chris Mason
2011-06-20 1:12 Chris Mason
2011-06-12 11:57 Chris Mason
2011-06-12 18:08 ` Linus Torvalds
2011-06-13 1:02 ` Andi Kleen
2011-06-13 1:52 ` Chris Mason
2011-06-13 2:05 ` Li Zefan
2011-06-04 14:37 Chris Mason
2011-05-27 19:55 Chris Mason
2011-05-27 21:44 ` Chester
2011-05-15 14:47 Chris Mason
2011-05-15 15:41 ` kehon
2011-04-26 14:24 Chris Mason
2011-04-18 14:26 Chris Mason
2011-02-15 3:49 Chris Mason
2011-02-07 20:12 Chris Mason
2011-02-08 20:05 ` Helmut Hullen
2010-12-14 1:54 Chris Mason
2010-05-27 15:15 Chris Mason
2010-05-27 17:18 ` Linus Torvalds
2010-05-27 17:32 ` Chris Mason
2010-05-27 17:47 ` Linus Torvalds
2010-06-02 2:59 ` Miao Xie
2010-09-12 12:38 ` Felipe Contreras
2010-04-05 19:36 Chris Mason
2010-04-06 15:40 ` Chris Mason
2010-03-15 19:18 Chris Mason
2010-03-16 21:01 ` Chris Mason
2010-03-18 16:59 ` Chris Mason
2009-10-15 0:06 Chris Mason
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='AANLkTimcLOFoJ8m2PBG9nsfw4L3FGPNa+RN=Cj_-nZdC@mail.gmail.com' \
--to=mitch.harder@sabayonlinux.org \
--cc=anthony@extof.me \
--cc=felixblanke@gmail.com \
--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).