All of lore.kernel.org
 help / color / mirror / Atom feed
From: bepi@adria.it
To: linux-btrfs@vger.kernel.org
Subject: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Mon, 21 Nov 2016 13:09:15 +0100	[thread overview]
Message-ID: <1479730155.5832e3eb3fde8@webmail.adria.it> (raw)

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.

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


             reply	other threads:[~2016-11-21 12:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 12:09 bepi [this message]
2016-11-26 14:56 ` [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive 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
2016-12-19 12:54   ` bepi
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=1479730155.5832e3eb3fde8@webmail.adria.it \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.