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/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
