All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: cwillu <cwillu@cwillu.com>
Cc: Chris Mason <chris.mason@oracle.com>,
	Mitch Harder <mitch.harder@sabayonlinux.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support
Date: Fri, 24 Dec 2010 14:55:53 +0800	[thread overview]
Message-ID: <4D1443F9.4040001@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTi=jGNaV-Sm+GsCHtwGx1UkG8bUyvGgz+2KLPgUT@mail.gmail.com>

cwillu wrote:
> On Wed, Nov 17, 2010 at 8:08 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>> Hi Chris,
>>
>> Here's the updated patchset. As I still haven't got a kernel.org
>> account, I have set up a git tree in another public git repository,
>> and I'll use it for now.
>>
>> You can pull from:
>>
>>        git://repo.or.cz/linux-btrfs-devel.git lzo-support
>>
>>
>> Lzo is a much faster compression algorithm than gzib, so would allow
>> more users to enable transparent compression, and some users can
>> choose from compression ratio and compression speed.
>>
>> Usage:
>>
>> # mount -t btrfs -o compress[=<zlib,lzo>] dev /mnt
>> or
>> # mount -t btrfs -o compress-force[=<zlib,lzo>] dev /mnt
>>
>> "-o compress" without argument is still allowed for compatability.
> 
> This doesn't seem to work with -o remount.  "mount / -o
> remount,compress=lzo" fails with "[90192.345382] btrfs: unrecognized
> mount option 'compress=lzo'".  The -clzo option to defrag works fine.
> 

It works for me:

# mount -t btrfs -o compress=zlib /dev/loop1 /mnt
# mount -o remount,compress=lzo /dev/loop1 /mnt
# dmesg
...
device fsid c142fef10429f78f-540f99158993f7a2 devid 1 transid 31 /dev/loop1
btrfs: use zlib compression
btrfs: use lzo compression

  reply	other threads:[~2010-12-24  6:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  2:08 [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support Li Zefan
2010-11-18  2:09 ` [PATCH v2 1/6] btrfs: Fix bugs in zlib workspace Li Zefan
2010-11-18  2:10 ` [PATCH v2 2/6] btrfs: Fix error handling in zlib Li Zefan
2010-11-18  2:10 ` [PATCH v2 3/6] btrfs: Allow to add new compression algorithm Li Zefan
2010-11-18  2:10 ` [PATCH v2 4/6] btrfs: Add lzo compression support Li Zefan
2010-11-18  2:11 ` [PATCH v2 5/6] btrfs: Allow to specify compress method when defrag Li Zefan
2010-11-18  2:11 ` [PATCH v2 6/6] btrfs: Extract duplicate decompress code Li Zefan
2010-11-29 17:54 ` [GIT PULL][PATCH v2 0/6] btrfs: Add lzo compression support C Anthony Risinger
2010-11-30  1:00   ` Li Zefan
2010-11-30 17:12     ` C Anthony Risinger
2010-12-01  1:02       ` Li Zefan
2010-12-24  5:35 ` cwillu
2010-12-24  6:55   ` Li Zefan [this message]
2010-12-24 12:32     ` Chris Mason
2010-12-24 20:45       ` Chris Mason
2010-12-26  3:31         ` 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=4D1443F9.4040001@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=cwillu@cwillu.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 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.