Re: How to map extents to files

[Nikolaus Rath <Nikolaus@rath.org>]

On Jun 10 2016, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
> At 06/02/2016 10:56 PM, Nikolaus Rath wrote:
>> On Jun 02 2016, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
>>> At 06/02/2016 11:06 AM, Nikolaus Rath wrote:
>>>> Hello,
>>>>
>>>> For one of my btrfs volumes, btrfsck reports a lot of the following
>>>> warnings:
>>>>
>>>> [...]
>>>> checking extents
>>>> bad extent [138477568, 138510336), type mismatch with chunk
>>>> bad extent [140091392, 140148736), type mismatch with chunk
>>>> bad extent [140148736, 140201984), type mismatch with chunk
>>>> bad extent [140836864, 140865536), type mismatch with chunk
>>>> [...]
>>>>
>>>> Is there a way to discover which files are affected by this (in
>>>> particular so that I can take a look at them before and after a btrfsck
>>>> --repair)?
>>>
>>> Which version is the progs? If the fs is not converted from ext2/3/4,
>>> it may be a false alert.
>>
>> Version is 4.4.1. The fs may very well have been converted from ext4,
>> but I can't tell for sure.
>
> For such case, btrfsck --repair is unable to fix it, as btrfs-progs is
> not able to balance extents.
>
> Normally, a full balance would fix it.
>
>
> I would try to update btrfs-progs to 4.5 and recheck, to see if it's a
> false alert.
> If not, then remove unused snapshots and then do the full balance.

Newest btrfs-progs reported the same error, and a full balance fixed
it. Thank you!

Best,
Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«