From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: add support for mixed data+metadata block groups V3
Date: Wed, 20 Oct 2010 23:21:26 -0500 [thread overview]
Message-ID: <AANLkTi=9uDOLNk3JnLN=okVWwSZBvfpSdMwvAWkMJK0g@mail.gmail.com> (raw)
In-Reply-To: <1286452263-1635-1-git-send-email-josef@redhat.com>
I've been testing this patch (as well as the accompanying patch to btrfs-progs).
It seems to save a decent amount of space (maybe 10-20% according to
df in my testing, YMMV), but I was also noticing a performance penalty
of maybe 5-15%, depending on the application (in my case, I was timing
the untar-ing of data to a btrfs partition).
I also developed the perception that I was encountering some minor
latency issues when heavily using a drive formated for mixed data and
metadata (more keyboard and mouse hesitations than normal, difficult
stuff to quantify).
The main problem I encountered was a btrfs crash when booting with an
un-patched kernel, and letting the boot process attempt to mount the
drive with mixed data+metadata. I wasn't entirely surprised by this
result, but it was unclear from the patch description whether a volume
formatted with mixed data+metadata would be incompatible with an
un-patched, older kernel.
Other than that, it seemed to perform well. I did not encounter any
stability issues as long as I was using a patched kernel.
next prev parent reply other threads:[~2010-10-21 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 11:51 [PATCH] Btrfs: add support for mixed data+metadata block groups V3 Josef Bacik
2010-10-21 4:21 ` Mitch Harder [this message]
2010-10-21 15:46 ` David Nicol
2010-10-21 22:09 ` Diego Calleja
2010-10-21 22:21 ` Mitch Harder
2010-10-22 1:05 ` Josef Bacik
2010-10-22 1:32 ` C Anthony Risinger
2010-10-22 1:37 ` Josef Bacik
2010-10-22 2:06 ` C Anthony Risinger
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='AANLkTi=9uDOLNk3JnLN=okVWwSZBvfpSdMwvAWkMJK0g@mail.gmail.com' \
--to=mitch.harder@sabayonlinux.org \
--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).