From: Li Zefan <lizf@cn.fujitsu.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Problems Implementing Snappy Patches
Date: Thu, 16 Feb 2012 10:06:13 +0800 [thread overview]
Message-ID: <4F3C6495.60906@cn.fujitsu.com> (raw)
In-Reply-To: <CAKcLGm_AgoHWa1TGwxz6PfSkKvxmDXi_3ykHR10WgTFVW9Gt4g@mail.gmail.com>
Mitch Harder wrote:
> I've been trying to test the snappy compression patches, but I'm
> getting corruptions when trying to use snappy as built on my system.
>
> I'm checking out the Linux 3.2.6 kernel, merging that with the latest
> 'for-linus' branch on Chris Mason's kernel.org repo, and then
> integrating the snappy and lz4 patches from David Sterba's git
> repository (dev/compression-squad branch).
>
> I've tried a simple merge of the dev/compression-squad branch (which
> merged without complaint by git), and I also tried a second build of
> the kernel integrating the dev/compression-squad branch patches with
> format-patch (git format-patch -k -m -U5 --stdout <range> | git am -3
> -k).
>
> I've also tried sourcing my snappy patches from Chris Mason's snappy
> branch on kernel.org with the same result.
>
A month ago I saved emails as patches and applied them on linux-btrfs'
for-linus branch, and I got the same problem. Then I used the snappy
branch (plus my fix), and it was fine. Don't know why.
> I get the same results either way.
>
> My system is a Core 2 Duo x86_64 Sabayon based system (Gentoo is our
> parent distro). My target btrfs/snappy partition is a 16 GB partition
> I use for testing on a 500GB Western Digital Hard Drive.
>
> When I copy directory containing a kernel sources git repository to a
> freshly formated partition mounted with snappy, I get a corrupted
> copy. If I mount with lzo or lz4 compression, I don't see any
> corruptions from the copy.
>
> I'm not showing any errors in dmesg.
>
You're not seeing any errors, right?
next prev parent reply other threads:[~2012-02-16 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 22:46 Problems Implementing Snappy Patches Mitch Harder
2012-02-15 23:03 ` Duncan
2012-02-15 23:14 ` Mitch Harder
2012-02-16 2:06 ` Li Zefan [this message]
2012-02-16 13:01 ` Mitch Harder
2012-02-16 13:15 ` David Sterba
2012-02-17 0:10 ` Mitch Harder
2012-02-21 12:03 ` David Sterba
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=4F3C6495.60906@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).