From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <bepi@adria.it>, <linux-btrfs@vger.kernel.org>
Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Mon, 19 Dec 2016 12:53:45 +0800 [thread overview]
Message-ID: <83dbcf2c-df10-5628-fc46-9d33a7bf78af@cn.fujitsu.com> (raw)
In-Reply-To: <1479730155.5832e3eb3fde8@webmail.adria.it>
At 11/21/2016 08:09 PM, bepi@adria.it wrote:
> Hi.
>
> My system: Fedora 23, kernel-4.7.10-100.fc23.x86_64 btrfs-progs-4.4.1-1.fc23.x86_64
>
> Testing the remote differential receive (via ssh and in local network) of 24
> sequential snapshots, and simultaneously deleting the snapshot, (in the same
> file system, but in a different subvolume), there has been an file access error,
> and the file system has corrupt.
Are you using qgroup?
IIRC, Filipe fixed a problem which could cause backref corruption which
only happens if quota is enabled.
Thanks,
Qu
>
> Both scrub, both recovery and clear_cache mount options, both btrfsck, have
> failed, the file system is left in a state unusable.
>
> After reformatting the filesystem, remote receive of 24 snapshots worked properly.
>
> The file system is used exclusively for receive the snapshot, it is composed of
> a single device.
> The initial snapshot is a linux installation of 50Gb.
>
>
> I think that there was a race condition between the receive and deletion of
> snapshots (that were performed on two different subvolume).
>
>
> Best regards.
>
> gdb
>
> ----------------------------------------------------
> This mail has been sent using Alpikom webmail system
> http://www.alpikom.it
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2016-12-19 4:53 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
2016-12-19 4:53 ` Qu Wenruo [this message]
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=83dbcf2c-df10-5628-fc46-9d33a7bf78af@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=bepi@adria.it \
--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).