From: Tomasz Chmielewski <tch@virtall.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: compression disk space saving - what are your results?
Date: Wed, 02 Dec 2015 23:06:27 +0900 [thread overview]
Message-ID: <444beddc07dce88fd81eeabdaa060f29@admin.virtall.com> (raw)
In-Reply-To: <CAP9B-Qm8gQdCZzQuMeZWCY=ni-xEBOueZpFPrYHMpcwdjtVC5Q@mail.gmail.com>
On 2015-12-02 23:03, Wang Shilong wrote:
>> Compression ratio is much much better now (on a slightly changed data
>> set):
>>
>> # df -h
>> /dev/xvdb 200G 24G 176G 12% /var/log/remote
>>
>>
>> # du -sh /var/log/remote/
>> 138G /var/log/remote/
>>
>>
>> So, 138 GB files use just 24 GB on disk - nice!
>>
>> However, I would still expect that compress=zlib has almost the same
>> effect
>> as compress-force=zlib, for 100% text files/logs.
>
> btw, what is your kernel version? there was a bug that detected inode
> compression
> ration wrong.
>
> http://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?id=68bb462d42a963169bf7acbe106aae08c17129a5
> http://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?id=4bcbb33255131adbe481c0467df26d654ce3bc78
Linux 4.3.0.
Tomasz Chmielewski
http://wpkg.org/
next prev parent reply other threads:[~2015-12-02 14:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 9:46 compression disk space saving - what are your results? Tomasz Chmielewski
2015-12-02 10:36 ` Duncan
2015-12-02 14:03 ` Imran Geriskovan
2015-12-02 14:39 ` Austin S Hemmelgarn
2015-12-03 6:29 ` Duncan
2015-12-03 12:09 ` Imran Geriskovan
2015-12-04 12:33 ` Austin S Hemmelgarn
2015-12-04 12:37 ` Austin S Hemmelgarn
2015-12-02 13:03 ` Austin S Hemmelgarn
2015-12-02 13:53 ` Tomasz Chmielewski
2015-12-02 14:03 ` Wang Shilong
2015-12-02 14:06 ` Tomasz Chmielewski [this message]
2015-12-02 14:49 ` Austin S Hemmelgarn
2015-12-22 3:55 ` Kai Krakow
2015-12-22 17:25 ` james northrup
2015-12-05 13:37 ` Marc Joliet
2015-12-05 14:11 ` Marc Joliet
2015-12-06 4:21 ` Duncan
2015-12-06 11:26 ` Marc Joliet
2015-12-05 19:38 ` guido_kuenne
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=444beddc07dce88fd81eeabdaa060f29@admin.virtall.com \
--to=tch@virtall.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.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.