From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: Btrfs progs release 4.1
Date: Wed, 9 Sep 2015 10:01:25 -0400 [thread overview]
Message-ID: <55F03BB5.3050506@gmail.com> (raw)
In-Reply-To: <20150909132544.GH8891@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On 2015-09-09 09:25, David Sterba wrote:
> On Wed, Sep 09, 2015 at 11:24:17AM +0800, Qu Wenruo wrote:
>> The problem is that, for converted image, it's quite possible that data
>> and metadata extent are stored in one chunk even the chunk is not mixed.
>>
>> I'll add fsck support for it soon.
>
> That would be great, I have no idea how the data/metadata can get mixed.
> Does this involve inlied file data that come from ext4?
Hmm, I'm actually kind of curious about this too. AFAIK, the inline
file data limit on ext* is significantly smaller than on btrfs. I could
possibly see a really badly fragmented ext* filesystem causing this to
happen because of the chunk size requirements in btrfs, but I would
expect such a case to fail in new and unexpected ways as a result.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-09 14:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:00 Btrfs progs release 4.1 David Sterba
2015-06-22 16:18 ` Goffredo Baroncelli
2015-06-22 18:01 ` David Sterba
2015-06-22 18:18 ` qgroup limit clearing, was " Christian Robottom Reis
2015-06-22 23:55 ` Tsutomu Itoh
2015-06-23 1:55 ` Qu Wenruo
2015-06-23 12:42 ` David Sterba
2015-06-22 18:18 ` Christian Robottom Reis
2015-06-22 20:45 ` Martin Steigerwald
2015-06-23 12:53 ` David Sterba
2015-06-23 9:03 ` Sjoerd
2015-06-23 9:18 ` Qu Wenruo
2015-06-23 14:45 ` David Sterba
2015-06-24 20:26 ` Sjoerd
2015-06-25 13:03 ` David Sterba
2015-09-09 1:34 ` Qu Wenruo
2015-09-09 3:24 ` Qu Wenruo
2015-09-09 10:35 ` Vytautas D
2015-09-09 11:25 ` Duncan
2015-09-09 13:26 ` David Sterba
2015-09-09 13:25 ` David Sterba
2015-09-09 14:01 ` Austin S Hemmelgarn [this message]
2015-09-10 0:50 ` Qu Wenruo
2015-09-09 13:19 ` David Sterba
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=55F03BB5.3050506@gmail.com \
--to=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).