From: bepi@adria.it
To: Xin Zhou <xin.zhou@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Wed, 21 Dec 2016 13:27:02 +0100 [thread overview]
Message-ID: <1482323222.585a7516d6aa4@webmail.adria.it> (raw)
In-Reply-To: <trinity-f5b0b96e-286c-4485-a02e-1f96bca7a906-1482255789582@3capp-mailcom-bs06>
Hi.
I will insert ' btrfs check ' after each ' receive ' in my script.
I will test again my hardware.
But is not very likely that 2 computers, 3 HDD, 3 partitions, all have issue.
I think that the problem is a concomitance of operations, a race condition, a
random conditions.
I'll try to create a test case.
P.S. For find the problem may need to insert tools as ' coredumper ' and '
sanitize ' in ' btrfs ', detect in realtime the ' extent ' corruption, and log
detection.
Thank you.
Gdb
Xin Zhou <xin.zhou@gmx.com>:
> 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
> Â
> Â
>
> Sent:Â Monday, December 19, 2016 at 10:55 AM
> From:Â "Giuseppe Della Bianca" <bepi@adria.it>
> To:Â "Xin Zhou" <xin.zhou@gmx.com>
> Cc:Â linux-btrfs@vger.kernel.org
> Subject:Â Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system
> during the snapshot receive
> a concrete example
>
>
> SNAPSHOT
>
> /dev/nvme0n1p2 on /tmp/tmp.X3vU6dLLVI type btrfs
> (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
>
> btrfsManage SNAPSHOT /
>
> (2016-12-19 19:44:00) Start btrfsManage
> . . . Start managing SNAPSHOT ' / ' filesystem ' root ' snapshot
>
> In ' btrfssnapshot ' latest source snapshot ' root-2016-12-18_15:10:01.40 '
> . . . date ' 2016-12-18_15:10:01 ' number ' 40 '
>
> Creation ' root-2016-12-19_19:44:00.part ' snapshot from ' root ' subvolume
> . . . Create a readonly snapshot of '/tmp/tmp.X3vU6dLLVI/root' in
> '/tmp/tmp.X3vU6dLLVI/btrfssnapshot/root/root-2016-12-19_19:44:00.part'
>
> Renaming ' root-2016-12-19_19:44:00.part ' into ' root-2016-12-19_19:44:00.41
> ' snapshot
>
> Source snapshot list of ' root ' subvolume
> . . . btrfssnapshot/root/root-2016-08-28-12-35-01.1
> ]zac[
> . . . btrfssnapshot/root/root-2016-12-19_19:44:00.41
>
> (2016-12-19 19:44:05) End btrfsManage
> . . . End managing SNAPSHOT ' / ' filesystem ' root ' snapshot
> CORRECTLY
>
>
>
> SEND e RECEIVE
>
> /dev/nvme0n1p2 on /tmp/tmp.o78czE0Bo6 type btrfs
> (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
> /dev/sda2 on /tmp/tmp.XcwqQCKq09 type btrfs
> (rw,relatime,space_cache,subvolid=5,subvol=/)
>
> btrfsManage SEND / /dev/sda2
>
> (2016-12-19 19:47:24) Start btrfsManage
> . . . Start managing SEND ' / ' filesystem ' root ' snapshot in ' /dev/sda2
> '
>
> Sending ' root-2016-12-19_19:44:00.41 ' source snapshot to ' btrfsreceive '
> subvolume
> . . . btrfs send -p
> /tmp/tmp.o78czE0Bo6/btrfssnapshot/root/root-2016-12-18_15:10:01.40
> /tmp/tmp.o78czE0Bo6/btrfssnapshot/root/root-2016-12-19_19:44:00.41 | btrfs
> receive /tmp/tmp.XcwqQCKq09/btrfsreceive/root/.part/
> . . . At subvol
> /tmp/tmp.o78czE0Bo6/btrfssnapshot/root/root-2016-12-19_19:44:00.41
> . . . At snapshot root-2016-12-19_19:44:00.41
>
> Creation ' root-2016-12-19_19:44:00.41 ' snapshot from '
> .part/root-2016-12-19_19:44:00.41 ' subvolume
> . . . Create a readonly snapshot of
> '/tmp/tmp.XcwqQCKq09/btrfsreceive/root/.part/root-2016-12-19_19:44:00.41' in
> '/tmp/tmp.XcwqQCKq09/btrfsreceive/root/root-2016-12-19_19:44:00.41'
> . . . Delete subvolume (commit):
> '/tmp/tmp.XcwqQCKq09/btrfsreceive/root/.part/root-2016-12-19_19:44:00.41'
>
> Snapshot list in ' /dev/sda2 ' device
> . . . btrfsreceive/data_backup/data_backup-2016-12-17_12:07:00.1
> . . . btrfsreceive/data_storage/data_storage-2016-12-10_17:05:51.1
> . . . btrfsreceive/root/root-2016-08-28-12-35-01.1
> ]zac[
> . . . btrfsreceive/root/root-2016-12-19_19:44:00.41
>
> (2016-12-19 19:48:37) End btrfsManage
> . . . End managing SEND ' / ' filesystem ' root ' snapshot in ' /dev/sda2 '
> CORRECTLY
>
>
>
> > Hi Giuseppe,
> >
> > Would you like to tell some details about:
> > 1. the XYZ snapshot was taken from which subvolume
> > 2. where the base (initial) snapshot is stored
> > 3. The 3 partitions receives the same snapshot, are they in the same btrfs
> > configuration and subvol structure?
> >
> > Also, would you send the link reports "two files unreadable error" post
> > mentioned in step 2? Hope can see the message and figure out if the issue
> > first comes from sender or receiver side.
> >
> > Thanks,
> > Xin
> >
> >
> Â
>
----------------------------------------------------
This mail has been sent using Alpikom webmail system
http://www.alpikom.it
next prev parent reply other threads:[~2016-12-21 12:27 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 [this message]
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
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=1482323222.585a7516d6aa4@webmail.adria.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).