From: Liu Bo <bo.li.liu@oracle.com>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs allow compression on NoDataCow files? (AFAIK Not, but it does)
Date: Tue, 2 Jan 2018 11:44:13 -0700 [thread overview]
Message-ID: <20180102184413.GC22892@dhcp-10-211-47-181.usdhcp.oraclecorp.com> (raw)
In-Reply-To: <CAGqmi740EcovePxQswsZ=yh9E5Y1zLKCBaTvFN0EE_AuVPpQ7A@mail.gmail.com>
On Wed, Dec 20, 2017 at 11:59:20PM +0300, Timofey Titovets wrote:
> How reproduce:
> touch test_file
> chattr +C test_file
> dd if=/dev/zero of=test_file bs=1M count=1
> btrfs fi def -vrczlib test_file
> filefrag -v test_file
>
> test_file
> Filesystem type is: 9123683e
> File size of test_file is 1048576 (256 blocks of 4096 bytes)
> ext: logical_offset: physical_offset: length: expected: flags:
> 0: 0.. 31: 72917050.. 72917081: 32: encoded
> 1: 32.. 63: 72917118.. 72917149: 32: 72917082: encoded
> 2: 64.. 95: 72919494.. 72919525: 32: 72917150: encoded
> 3: 96.. 127: 72927576.. 72927607: 32: 72919526: encoded
> 4: 128.. 159: 72943261.. 72943292: 32: 72927608: encoded
> 5: 160.. 191: 72944929.. 72944960: 32: 72943293: encoded
> 6: 192.. 223: 72944952.. 72944983: 32: 72944961: encoded
> 7: 224.. 255: 72967084.. 72967115: 32: 72944984:
> last,encoded,eof
> test_file: 8 extents found
>
> I can't found at now, where that error happen in code,
> but it's reproducible on Linux 4.14.8
>
Please check the comments in this function need_force_cow(),
* Force cow if given extent needs to be defragged.
and using zlib makes it compress the data.
Thanks,
-liubo
prev parent reply other threads:[~2018-01-02 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 20:59 Btrfs allow compression on NoDataCow files? (AFAIK Not, but it does) Timofey Titovets
2017-12-21 18:51 ` Chris Mason
2017-12-22 23:58 ` Kai Krakow
2018-01-02 18:44 ` Liu Bo [this message]
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=20180102184413.GC22892@dhcp-10-211-47-181.usdhcp.oraclecorp.com \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@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 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).