From: Liu Bo <bo.li.liu@oracle.com>
To: Ivan Sizov <sivan606@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/6] add sanity check for extent inline ref type
Date: Thu, 1 Jun 2017 15:57:29 -0700 [thread overview]
Message-ID: <20170601225729.GA3279@lim.localdomain> (raw)
In-Reply-To: <CAMG9ccwxQn172kpUR61hp8OV_H+rRx4BQhRvMpUs4qn4DKic+Q@mail.gmail.com>
On Thu, Jun 01, 2017 at 11:26:26PM +0300, Ivan Sizov wrote:
> 2017-06-01 20:35 GMT+03:00 Liu Bo <bo.li.liu@oracle.com>:
> > After I went through the output of leaf's content, most parts of the
> > leaf is sane except the two corrupted items, it's still not clear to
> > me what caused the corruption, there could be some corner cases that
> > I'm not aware of.
> >
> > If fsck doesn't work for you, then a recovery from backup may be the
> > best option.
>
> I don't need to run any repair procedures because system is working
> normally. Most likely that corrupted extents belong to files located
> somewhere in /home.
> Do you mean I should run fsck in order to determine which files are
> corrupted? What are proper options to run fsck with?
I see. Scrub has found that there are some corrupted metadata, if you
want to fix that corrupted thing, fsck may be helpful. Due to my
test, 'btrfs check /your_disk' fixed my corruption.
With this patch set, at least you won't get a crash when accessing the
corrupted extent inline ref.
-liubo
next prev parent reply other threads:[~2017-06-01 22:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 0:26 [PATCH 0/6] add sanity check for extent inline ref type Liu Bo
2017-05-26 0:26 ` [PATCH 1/6] Btrfs: add a helper to retrive " Liu Bo
2017-05-26 7:09 ` Nikolay Borisov
2017-05-26 17:44 ` Jeff Mahoney
2017-05-26 18:13 ` David Sterba
2017-05-26 18:15 ` David Sterba
2017-05-26 0:26 ` [PATCH 2/6] Btrfs: convert to use btrfs_get_extent_inline_ref_type Liu Bo
2017-05-26 0:26 ` [PATCH 3/6] Btrfs: remove BUG() in btrfs_extent_inline_ref_size Liu Bo
2017-05-26 0:26 ` [PATCH 4/6] Btrfs: remove BUG() in print_extent_item Liu Bo
2017-05-26 18:18 ` David Sterba
2017-05-26 19:52 ` Liu Bo
2017-05-26 0:26 ` [PATCH 5/6] Btrfs: remove BUG() in add_data_reference Liu Bo
2017-05-26 18:20 ` David Sterba
2017-05-26 20:01 ` Liu Bo
2017-05-26 0:26 ` [PATCH 6/6] Btrfs: add sanity check of extent item in scrub Liu Bo
2017-05-26 18:33 ` David Sterba
2017-05-26 20:20 ` Liu Bo
2017-05-29 1:48 ` Qu Wenruo
2017-05-29 13:49 ` David Sterba
2017-05-30 14:05 ` [PATCH 0/6] add sanity check for extent inline ref type Ivan Sizov
2017-05-30 18:02 ` Liu Bo
2017-05-30 18:57 ` Ivan Sizov
2017-06-01 17:35 ` Liu Bo
2017-06-01 20:26 ` Ivan Sizov
2017-06-01 22:57 ` Liu Bo [this message]
2017-06-19 9:06 ` Ivan Sizov
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=20170601225729.GA3279@lim.localdomain \
--to=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sivan606@gmail.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).