From: Marek Behun <marek.behun@nic.cz>
To: linux-btrfs@vger.kernel.org
Subject: Can a compressed file extent have non-zero offset?
Date: Wed, 30 Aug 2017 01:07:56 +0200 [thread overview]
Message-ID: <20170830010756.05d8f9f3@nic.cz> (raw)
Hello,
I cannot find this in the documentation (and the sources are too long),
so I am trying here:
can a file_extent_item with
item.type == BTRFS_FILE_EXTENT_REG
and
item.compression != BTRFS_COMPRESS_NONE
have non zero offset (item.offset != 0) ?
What does it mean in such a case? That compressed data start at 0, but
in the uncompressed data, the data begin at item.offset? What does
item.num_bytes in this case mean - the valid number of bytes from
position item.offset, or the number of all bytes, even those before
position item.offset?
Thank you.
Marek
reply other threads:[~2017-08-29 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170830010756.05d8f9f3@nic.cz \
--to=marek.behun@nic.cz \
--cc=linux-btrfs@vger.kernel.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).