From: Nikolaus Rath <Nikolaus@rath.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: How to map extents to files
Date: Thu, 02 Jun 2016 07:56:35 -0700 [thread overview]
Message-ID: <87zir3skpo.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <06ef9ac3-ed15-9621-9629-4c8965618db6@cn.fujitsu.com> (Qu Wenruo's message of "Thu, 2 Jun 2016 12:01:55 +0800")
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.
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.«
next prev parent reply other threads:[~2016-06-02 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 3:06 How to map extents to files Nikolaus Rath
2016-06-02 4:01 ` Qu Wenruo
2016-06-02 14:56 ` Nikolaus Rath [this message]
2016-06-10 8:17 ` Qu Wenruo
2016-06-10 15:38 ` Henk Slager
2016-06-14 15:04 ` Nikolaus Rath
2016-06-10 3:03 ` Nikolaus Rath
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=87zir3skpo.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.