From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: corruption: yet another one after deleting a ro snapshot
Date: Wed, 18 Jan 2017 02:20:18 +0100 [thread overview]
Message-ID: <1484702418.7262.42.camel@scientia.net> (raw)
In-Reply-To: <cacc3a27-6fcb-9ba9-2959-099145c34bad@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Wed, 2017-01-18 at 08:41 +0800, Qu Wenruo wrote:
> Since we have your extent tree and root tree dump, I think we should
> be
> able to build a image to reproduce the case.
+1
> BTW, your fs is too large for us to really do some verification or
> other
> work.
Sure I know... but that's simply the one which I work the most with and
where I stumble over such things.
I have e.g. a smaller one (well still 1TB in total 500GB used) which is
the root-fs from my notebook... but not really any issues with that so
far ^^
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-01-18 1:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 1:07 corruption: yet another one after deleting a ro snapshot Christoph Anton Mitterer
2017-01-12 1:13 ` Christoph Anton Mitterer
2017-01-12 1:25 ` Qu Wenruo
2017-01-12 2:28 ` Christoph Anton Mitterer
2017-01-12 2:38 ` Qu Wenruo
2017-01-15 17:04 ` Christoph Anton Mitterer
2017-01-16 1:38 ` Qu Wenruo
2017-01-16 2:56 ` Christoph Anton Mitterer
2017-01-16 3:16 ` Qu Wenruo
2017-01-16 4:53 ` Christoph Anton Mitterer
2017-01-16 5:47 ` Qu Wenruo
2017-01-16 22:07 ` Christoph Anton Mitterer
2017-01-17 8:53 ` Qu Wenruo
2017-01-17 10:39 ` Christoph Anton Mitterer
2017-01-18 0:41 ` Qu Wenruo
2017-01-18 1:20 ` Christoph Anton Mitterer [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 10:27 Giuseppe Della Bianca
2017-01-16 11:06 Giuseppe Della Bianca
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=1484702418.7262.42.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).