From: Roman Mamedov <rm@romanrm.net>
To: Dmitrii Tcvetkov <demfloro@demfloro.ru>
Cc: "Scott E. Blomquist" <sb@techsquare.com>, linux-btrfs@vger.kernel.org
Subject: Re: trouble mounting btrfs filesystem....
Date: Wed, 15 Aug 2018 01:11:28 +0500 [thread overview]
Message-ID: <20180815011128.344af7c4@natsu> (raw)
In-Reply-To: <20180814164111.76653189@job.localdomain>
On Tue, 14 Aug 2018 16:41:11 +0300
Dmitrii Tcvetkov <demfloro@demfloro.ru> wrote:
> If usebackuproot doesn't help then filesystem is beyond repair and you
> should try to refresh your backups with "btrfs restore" and restore from them[1].
>
> [1] https://btrfs.wiki.kernel.org/index.php/FAQ#How_do_I_recover_from_a_.22parent_transid_verify_failed.22_error.3F
This is really the worst unfixed Btrfs issue today. This happens a lot on
unclean shutdowns or reboots, and the only advice is usually to "start over"
-- even if your FS is 40 TB and the discrepancy is just by half a dozen
transids. There needs to be a way in fsck to accept (likely minor!) FS damage
and forcefully fixup transids to what they should be -- or even nuke the
affected portions entirely.
--
With respect,
Roman
next prev parent reply other threads:[~2018-08-14 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 19:19 trouble mounting btrfs filesystem Scott E. Blomquist
2018-08-14 12:39 ` Scott E. Blomquist
2018-08-14 13:00 ` Dmitrii Tcvetkov
2018-08-14 13:31 ` Scott E. Blomquist
2018-08-14 13:41 ` Dmitrii Tcvetkov
2018-08-14 13:51 ` Scott E. Blomquist
2018-08-14 20:11 ` Roman Mamedov [this message]
2018-08-14 15:16 ` Hans van Kranenburg
2018-08-14 17:09 ` Andrei Borzenkov
2018-08-14 23:11 ` Hans van Kranenburg
2018-08-14 15:13 ` Hans van Kranenburg
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=20180815011128.344af7c4@natsu \
--to=rm@romanrm.net \
--cc=demfloro@demfloro.ru \
--cc=linux-btrfs@vger.kernel.org \
--cc=sb@techsquare.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).