Hi. LOCAL "btrfs send/receive" btrfs send -p /tmp/tmp.hkAa8XaliZ/btrfssnapshot/root/root-2016-12-18_15:10:01.40 /tmp/tmp.hkAa8XaliZ/btrfssnapshot/root/root-2016-12-19_19:44:00.41 | btrfs receive /tmp/tmp.NRYgYVC3p6/btrfsreceive/root/.part/ REMOTE "btrfs send/receive" btrfs send -p /tmp/tmp.BTACBk7xuK/btrfssnapshot/root/root-2016-12-18_15:10:01.40 /tmp/tmp.BTACBk7xuK/btrfssnapshot/root/root-2016-12-19_19:44:00.41 | ssh root@xxxxxxxxxxxxxxx btrfsManage REMOTE_RECEIVE /dev/sda3 root root-2016-12-19_19:44:00.41 Remote btrfsManage script (btrfsManage REMOTE_RECEIVE /dev/sda3 root root-2016-12-19_19:44:00.41) executes cat - | btrfs receive /tmp/tmp.Wd5togIiaL/btrfsreceive/root/.part/ The waiting for the end of a command, in shell script, is implicit/automatic. Regards. Gdb > Hi, > > Would you like to show the "btrfs send/receive" command the script are > using, including all the parameters, and how the script waits for a > completion of a transfer. > > From the beginning of the thread, it seems the transfer tests are going > through different network environment. > Thanks, > Xin > > Sent: Friday, December 23, 2016 at 9:48 AM > From: bepi@xxxxxxxx > To: "Xin Zhou" <xin.zhou@xxxxxxx> > Cc: "Btrfs BTRFS" <linux-btrfs@xxxxxxxxxxxxxxx> > Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system > during the snapshot receive Yes. > > Is through to the btrfs-tools error message that the script has printed, > that I realized the filesystem corruption. > > > P.S. Various messages that you see in the working examples of the script, > are emitted directly by the btrfs-tools. > > > Gdb > > Xin Zhou <xin.zhou@xxxxxxx>: > > Hi, > > > > Does the script check the transfer status, and is there a transfer returns > > an error code? > > Thanks, > > Xin > >  > >  > > > > Sent: Thursday, December 22, 2016 at 11:28 PM > > From: "Giuseppe Della Bianca" <bepi@xxxxxxxx> > > To: "Btrfs BTRFS" <linux-btrfs@xxxxxxxxxxxxxxx> > > Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file > > system during the snapshot receive > > (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@xxxxxxxxxxxxxxxxx> > > > To: No recipient address > > > Cc: "Giuseppe Della Bianca" <bepi@xxxxxxxx>, "Xin Zhou" > > > > <xin.zhou@xxxxxxx>, > > > > > "Btrfs BTRFS" <linux-btrfs@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxx> > > > > 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 > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > ---------------------------------------------------- > This mail has been sent using Alpikom webmail system > http://www.alpikom.it[http://www.alpikom.it] > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
