Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Paul Jones <paul@pauljones.id.au>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Help with leaf parent key incorrect
Date: Mon, 26 Feb 2018 16:26:43 +0800	[thread overview]
Message-ID: <2fd186fe-34b3-c2dd-ad36-a043368104eb@oracle.com> (raw)
In-Reply-To: <ME1PR01MB0338086CF4FF5F185BA52C029EC10@ME1PR01MB0338.ausprd01.prod.outlook.com>



 > There is one io error in the log below,

Apparently, that's not a real EIO. We need to fix it.
But can't be the root cause we are looking for here.

----
 > Feb 24 22:41:59 home kernel: BTRFS: error (device dm-6) in 
btrfs_run_delayed_refs:3076: errno=-5 IO failure
 > Feb 24 22:41:59 home kernel: BTRFS info (device dm-6): forced readonly

static int run_delayed_extent_op(struct btrfs_trans_handle *trans,
                                  struct btrfs_fs_info *fs_info,
                                  struct btrfs_delayed_ref_head *head,
                                  struct btrfs_delayed_extent_op *extent_op)
{
::

                 } else {
                         err = -EIO;
                         goto out;
                 }
----

 > but other than that I have never had io errors before, or any other 
troubles.

  Hm. btrfs dev stat shows real disk IO errors.
  As this FS isn't mountable .. pls try
   btrfs dev stat <dev> > file
   search for 'device stats', there will be one for each disk.
  Or it reports in the syslog when it happens not necessarily
  during dedupe.

 > One of my other filesystems share the same two discs and it is still 
fine, so I think the hardware is probably ok.
  Right. I guess that too. A confirmation will be better.
 > I've copied the beginning of the errors below.


  At my end finding the root cause of 'parent transid verify failed'
  during/after dedupe is is kind of fading as disk seems to be had
  no issues. which I had in mind.

  Also, there wasn't abrupt power-recycle here? I presume.

  It's better to save the output disk1-log and disk2-log as below
  before further efforts to recovery. Just in case if something
  pops out.

   btrfs in dump-super -fa disk1 > disk1-log
   btrfs in dump-tree --degraded disk1 >> disk1-log [1]

   btrfs in dump-super -fa disk2 > disk2-log
   btrfs in dump-tree --degraded disk2 >> disk2-log [1]

  [1]
   --degraded option is in the ML.
   [PATCH] btrfs-progs: dump-tree: add degraded option

Thanks, Anand

  parent reply	other threads:[~2018-02-26  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 10:16 Help with leaf parent key incorrect Paul Jones
2018-02-26  4:02 ` Anand Jain
     [not found]   ` <ME1PR01MB0338086CF4FF5F185BA52C029EC10@ME1PR01MB0338.ausprd01.prod.outlook.com>
2018-02-26  8:26     ` Anand Jain [this message]
2018-02-27  5:27       ` Paul Jones

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=2fd186fe-34b3-c2dd-ad36-a043368104eb@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=paul@pauljones.id.au \
    /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