From: Giuseppe Della Bianca <bepi@adria.it>
To: xin.zhou@gmx.com, linux-btrfs@vger.kernel.org
Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Mon, 26 Dec 2016 12:24:43 +0100 [thread overview]
Message-ID: <1601097.j5XE6pKq09@exnet.gdb.it> (raw)
In-Reply-To: <trinity-f5b0b96e-286c-4485-a02e-1f96bca7a906-1482255789582@3capp-mailcom-bs06>
Hi.
I have executed the test that you have requested.
At this point I'm confused and demoralized
While 40 btrfs receive, btrfs check has reported many filesystem problems.
But at the end of all the btrfs receive, btrfs check did not find filesystem problem.
My tests have confirmed that the filesystem had no problems.
I think btrfs check detect false positives (this can change a repair in a destruction).
Regards.
Gdb
Xin Zhou Tue, 20 Dec 2016 09:47:01 -0800
>>Hi,
>>The system seems running some customized scripts continuously backup data from
>>a NVME drive to HDDs.
>>If the 3 HDDs backup storage are same in btrfs config, and the there is a bug
>>in btrfs code,
>>they all suppose to fail after the same operation sequence.
>>Otherwise, probably one of the HDDs might have issue, or there is a bug in
>>layer below btrfs.
>>For the customize script, it might be helpful to check the file system
>>consistency after each transfer.
>>That might be useful to figure out which step generates a corruption, and if
>>there is error propagations.
>>Regards,
>>Xin
next prev parent reply other threads:[~2016-12-26 11:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:09 [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive bepi
2016-11-26 14:56 ` Giuseppe Della Bianca
2016-11-26 18:56 ` Chris Murphy
2016-11-27 18:18 ` Giuseppe Della Bianca
2016-12-04 18:11 ` Giuseppe Della Bianca
2016-12-18 19:59 ` Giuseppe Della Bianca
2016-12-18 20:12 ` Chris Murphy
2016-12-18 21:36 ` Xin Zhou
2016-12-19 12:46 ` bepi
2016-12-19 13:04 ` bepi
2016-12-19 18:55 ` Giuseppe Della Bianca
2016-12-20 17:43 ` Xin Zhou
2016-12-21 12:27 ` bepi
2016-12-21 21:09 ` Chris Murphy
2016-12-21 21:11 ` Chris Murphy
2016-12-21 22:14 ` Xin Zhou
2016-12-23 7:28 ` Giuseppe Della Bianca
2016-12-23 16:53 ` Xin Zhou
2016-12-23 17:48 ` bepi
2016-12-23 18:35 ` Xin Zhou
2016-12-24 12:16 ` Giuseppe Della Bianca
2016-12-24 20:15 ` Xin Zhou
2016-12-25 22:57 ` Duncan
2016-12-26 2:36 ` Xin Zhou
2016-12-26 3:52 ` Duncan
2016-12-27 3:20 ` Xin Zhou
2016-12-26 11:04 ` Giuseppe Della Bianca
2016-12-26 17:41 ` Xin Zhou
2016-12-24 12:47 ` Giuseppe Della Bianca
2017-08-19 14:56 ` Giuseppe Della Bianca
2016-12-23 7:16 ` Giuseppe Della Bianca
2016-12-27 9:29 ` Giuseppe Della Bianca
2016-12-26 11:24 ` Giuseppe Della Bianca [this message]
2016-12-19 4:53 ` Qu Wenruo
2016-12-19 12:54 ` bepi
-- strict thread matches above, loose matches on Subject: below --
2016-11-22 13:19 bepi
[not found] <CAJCQCtRmmMc3QwhFAkGqFPLc1_C4VpZCei_cevncUJduTJmg@mail.gmail.com>
2016-12-18 20:39 ` 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=1601097.j5XE6pKq09@exnet.gdb.it \
--to=bepi@adria.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=xin.zhou@gmx.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).