All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Della Bianca <bepi@adria.it>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive
Date: Fri, 23 Dec 2016 08:28:19 +0100	[thread overview]
Message-ID: <21181187.lK0OKanLcd@exnet.gdb.it> (raw)
In-Reply-To: <trinity-6a0e983c-9cfd-479a-8f3a-593c8c30b7b0-1482358484582@3capp-mailcom-bs03>

(synthetic resend)

Hi.

Is possible that there are transfers, cancellations and other, at the same 
time, but not in the same subvolume.

My script checks that there are no transfers in progress on the same 
subvolume.

Is possible that the same subvolume is mounted several times (temporary mount 
at the beginning, and unmount at the end, in my script).


Thanks for all.


P.S. Sorry for my bad English.


Gdb


In data mercoledì 21 dicembre 2016 23:14:44, Xin Zhou ha scritto:
> Hi,
> Racing condition can happen, if running multiple transfers to the same
> destination. Would you like to tell how many transfers are the scripts
> running at a time to a specific hdd?
> 
> Thanks,
> Xin
>  
> 
> Sent: Wednesday, December 21, 2016 at 1:11 PM
> From: "Chris Murphy" <lists@colorremedies.com>
> To: No recipient address
> Cc: "Giuseppe Della Bianca" <bepi@adria.it>, "Xin Zhou" <xin.zhou@gmx.com>,
> "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> Subject: Re: [CORRUPTION
> FILESYSTEM] Corrupted and unrecoverable file system during the snapshot
> receive
> On Wed, Dec 21, 2016 at 2:09 PM, Chris Murphy <lists@colorremedies.com> 
wrote:
> > What about CONFIG_BTRFS_FS_CHECK_INTEGRITY? And then using check_int
> > mount option?
> 
> This slows things down, and in that case it might avoid the problem if
> it's the result of a race condition.
> 
> --
> Chris Murphy


  reply	other threads:[~2016-12-23  7:28 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 [this message]
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=21181187.lK0OKanLcd@exnet.gdb.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.