From: Alistair Grant <akgrant0710@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Fixing recursive fault and parent transid verify failed
Date: Mon, 7 Dec 2015 12:57:15 +1100 [thread overview]
Message-ID: <20151207015715.GA13954@alistair-xps13> (raw)
Hi,
(Resending as it looks like the first attempt didn't get through,
probably too large, so logs are now in dropbox)
I have a btrfs volume which is raid1 across two spinning rust disks,
each 2TB.
When trying to access some files from a another machine using sshfs the
server machine has crashed twice resulting in a hard lock up, i.e. power
off required to restart the machine.
There are no crash dumps in /var/log/syslog, or anything that looks like
an associated error message to me, however on the second occasion I was
able to see the following message flash up the console (in addition to
some stack dumps):
Fixing recursive fault, but reboot is needed
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?
I do have a backup of the drive (which I believe is completely up to
date, the btrfs volume is used for archiving media and documents, and
single person use of git repositories, i.e. only very light writing and
reading).
Some basic details:
OS: Ubuntu 15.10
Kernel: Ubuntu 4.2.0-19-generic (which is based on mainline 4.2.6)
> sudo btrfs fi df /srv/d2root
==============================
Data, RAID1: total=250.00GiB, used=248.86GiB
Data, single: total=8.00MiB, used=0.00B
System, RAID1: total=8.00MiB, used=64.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, RAID1: total=1.00GiB, used=466.77MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=160.00MiB, used=0.00B
> sudo btrfs fi usage /srv/d2root
=================================
Overall:
Device size: 3.64TiB
Device allocated: 502.04GiB
Device unallocated: 3.15TiB
Device missing: 0.00B
Used: 498.62GiB
Free (estimated): 1.58TiB (min: 1.58TiB)
Data ratio: 2.00
Metadata ratio: 1.99
Global reserve: 160.00MiB (used: 0.00B)
Data,single: Size:8.00MiB, Used:0.00B
/dev/sdc 8.00MiB
Data,RAID1: Size:250.00GiB, Used:248.86GiB
/dev/sdb 250.00GiB
/dev/sdc 250.00GiB
Metadata,single: Size:8.00MiB, Used:0.00B
/dev/sdc 8.00MiB
Metadata,RAID1: Size:1.00GiB, Used:466.77MiB
/dev/sdb 1.00GiB
/dev/sdc 1.00GiB
System,single: Size:4.00MiB, Used:0.00B
/dev/sdc 4.00MiB
System,RAID1: Size:8.00MiB, Used:64.00KiB
/dev/sdb 8.00MiB
/dev/sdc 8.00MiB
Unallocated:
/dev/sdb 1.57TiB
/dev/sdc 1.57TiB
btrfs scrub output:
https://www.dropbox.com/s/blqvopa1lhkghe5/scrub.log?dl=0
btrfsck sdb output:
https://www.dropbox.com/s/hw6w6cupuu1rny4/btrfsck.sdb.log?dl=0
btrfsck sdc output:
https://www.dropbox.com/s/mijz492mjr76p8z/btrfsck.sdc.log?dl=0
Thanks very much,
Alistair
next reply other threads:[~2015-12-07 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 1:57 Alistair Grant [this message]
2015-12-07 2:09 ` Fixing recursive fault and parent transid verify failed Lukas Pirl
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=20151207015715.GA13954@alistair-xps13 \
--to=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