On 2015-09-09 09:25, David Sterba wrote:
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.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?
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
