Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Lukas Pirl <btrfs@lukas-pirl.de>
To: linux-btrfs@vger.kernel.org
Cc: Alistair Grant <akgrant0710@gmail.com>
Subject: Re: Fixing recursive fault and parent transid verify failed
Date: Mon, 7 Dec 2015 15:09:32 +1300	[thread overview]
Message-ID: <5664EA5C.6050809@lukas-pirl.de> (raw)
In-Reply-To: <20151207015715.GA13954@alistair-xps13>

On 12/07/2015 02:57 PM, Alistair Grant wrote as excerpted:
> Fixing recursive fault, but reboot is needed

For the record:

I saw the same message (incl. hard lockup) when doing a balance on a
single-disk btrfs.

Besides that, the fs works flawlessly (~60GB, usage: no snapshots, ~15
lxc containers, low-load databases, few mails, a couple of Web servers).

As this is a production machine, I rather rebooted the machine instead
of investigating but the error is reproducible if that would be of
great interest.

> I've ran btrfs scrub and btrfsck on the drives, with the output
> included below.  Based on what I've found on the web, I assume that a
> btrfs-zero-log is required.
> 
> * Is this the recommended path?
> * Is there a way to find out which files will be affected by the loss of
>   the transactions?

> Kernel: Ubuntu 4.2.0-19-generic (which is based on mainline 4.2.6)

I used Debian Backports 4.2.6.

Cheers,

Lukas

  reply	other threads:[~2015-12-07  2:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07  1:57 Fixing recursive fault and parent transid verify failed Alistair Grant
2015-12-07  2:09 ` Lukas Pirl [this message]
2015-12-07  8:25 ` Duncan
2015-12-07 10:02   ` Alistair Grant
2015-12-07 13:48     ` Duncan
2015-12-07 19:55       ` Alistair Grant
2015-12-08 15:25         ` Duncan
2015-12-08 22:38           ` Alistair Grant
2015-12-09 10:19             ` Duncan
2015-12-12 22:12               ` Alistair Grant

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=5664EA5C.6050809@lukas-pirl.de \
    --to=btrfs@lukas-pirl.de \
    --cc=akgrant0710@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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