From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: parent transid verify failed on snapshot deletion
Date: Sun, 13 Mar 2016 17:03:54 +0000 (UTC) [thread overview]
Message-ID: <pan$a52ce$b1beae3d$57f5b99c$a796a0ec@cox.net> (raw)
In-Reply-To: 20160313142428.377b51b8@natsu
Roman Mamedov posted on Sun, 13 Mar 2016 14:24:28 +0500 as excerpted:
> With "Errors found in extent allocation tree", I wonder if I should try
> --init-extent-tree next.
With backups I'd try it, if only for the personal experience value and to
see what the result was. But that's certainly more intensive "surgery"
on the filesystem than --repair, and I'd only do it either for that
experience value or if I was seriously desperate to recover files, as I'd
not trust the filesystem's health after that intensive a surgery, and
would blow the filesystem away after I recovered what I needed, even if
it did appear to work successfully.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-03-13 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 15:48 parent transid verify failed on snapshot deletion Roman Mamedov
2016-03-12 17:15 ` Roman Mamedov
2016-03-13 9:24 ` Roman Mamedov
2016-03-13 17:03 ` Duncan [this message]
2016-03-13 17:24 ` Roman Mamedov
2016-03-13 20:10 ` Chris Murphy
2016-03-13 20:55 ` Roman Mamedov
2016-03-13 21:52 ` Chris Murphy
2016-03-17 8:39 ` Roman Mamedov
2016-03-13 3:54 ` Duncan
2016-03-13 20:54 ` Sylvain Joyeux
2016-03-17 8:32 ` "Fixed", " Roman Mamedov
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='pan$a52ce$b1beae3d$57f5b99c$a796a0ec@cox.net' \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).