Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Hi. Two news (one is OT and advertising to my btrfsManage script) I had to recreate from scratch two corrupted btrfs filesystems probably due to out of space during a snapshot receive. Almost it's a habit rebuild the filesystems after a few months. OT I have released the latest version of

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Hi. Only for information. I tried ' check_int ' mount option, but with a few tens of GB used, the kernel freezes completely (no ops, no messages, no panic, none). Thanks for all. Gdb P.S. Thanks and happy work to all. >>On Wed, Dec 21, 2016 at 2:09 PM, Chris Murphy

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

el.org Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive Xin Zhou posted on Mon, 26 Dec 2016 03:36:09 +0100 as excerpted: > One interesting thing to investigate might be the btrfs send / receive > result, under a disruptive network environment.

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

be in other place. Xin   Sent: Monday, December 26, 2016 at 3:04 AM From: "Giuseppe Della Bianca" <b...@adria.it> To: "Xin Zhou" <xin.z...@gmx.com>, "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Hi. I have executed the test that you have requested. At this point I'm confused and demoralized While 40 btrfs receive, btrfs check has reported many filesystem problems. But at the end of all the btrfs receive, btrfs check did not find filesystem problem. My tests have confirmed that the

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Hi. I agree with Duncan, and I add: - For remote transfer is used ssh. ssh is designed to ensure integrity of data. - Remote transfer uses a Gigabit Ethernet, it is never congested. - I had the same problems with a local btrfs receive. - The script currently has 907 lines of code, many of

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Xin Zhou posted on Mon, 26 Dec 2016 03:36:09 +0100 as excerpted: > One interesting thing to investigate might be the btrfs send / receive > result, under a disruptive network environment. If the connection breaks > in the middle of transfer (at different phase, maybe), see what could be > the

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

SYSTEM] Corrupted and unrecoverable file system during the snapshot receive Xin Zhou posted on Sat, 24 Dec 2016 21:15:40 +0100 as excerpted: > The code is relatively new to me, I did not see retry logic in stream > handling, please correct me if I am wrong about this. > So, I am not q

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Xin Zhou posted on Sat, 24 Dec 2016 21:15:40 +0100 as excerpted: > The code is relatively new to me, I did not see retry logic in stream > handling, please correct me if I am wrong about this. > So, I am not quite sure about the transfer behavior, if the system > subject to network issues in

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

day, December 23, 2016 at 9:48 AM > From: b...@adria.it > To: "Xin Zhou" <xin.z...@gmx.com> > Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> > Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system > during the snapshot receive Ye

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

onment.   Thanks, Xin Sent: Friday, December 23, 2016 at 9:48 AM From: b...@adria.it To: "Xin Zhou" <xin.z...@gmx.com> Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot r

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

ow 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" <li...@colorremedies.com> > > To: No recip

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

<li...@colorremedies.com> > To: No recipient address > Cc: "Giuseppe Della Bianca" <b...@adria.it>, "Xin Zhou" <xin.z...@gmx.com>, > "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> Subject: Re: [CORRUPTION > FILESYSTEM] Corrupted and unre

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

Della Bianca" <b...@adria.it>, "Xin Zhou" <xin.z...@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

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

(synthetic resend) I'll try to compile the kernel and mount with the config and option enabled. I keep in mind the side effects of that option. Thanks for all. P.S. Sorry for my bad English. Chris Murphy ha scritto: > On Wed, Dec 21, 2016 at 2:09 PM, Chris Murphy

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

rremedies.com> To: No recipient address Cc: "Giuseppe Della Bianca" <b...@adria.it>, "Xin Zhou" <xin.z...@gmx.com>, "Btrfs BTRFS" <linux-btrfs@vger.kernel.org> Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the sn

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

On Wed, Dec 21, 2016 at 2:09 PM, Chris Murphy 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

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

What about CONFIG_BTRFS_FS_CHECK_INTEGRITY? And then using check_int mount option? Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

ds, > Xin >   >   > > Sent: Monday, December 19, 2016 at 10:55 AM > From: "Giuseppe Della Bianca" <b...@adria.it> > To: "Xin Zhou" <xin.z...@gmx.com> > Cc: linux-btrfs@vger.kernel.org > Subject: Re: [CORRUPTION FILESYSTEM] Corrupted a

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

: Monday, December 19, 2016 at 10:55 AM From: "Giuseppe Della Bianca" <b...@adria.it> To: "Xin Zhou" <xin.z...@gmx.com> Cc: linux-btrfs@vger.kernel.org Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive a concrete ex

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

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

(Resend) Hi. It is a bit complex. Primary system subvolume on SSD devices on PCIe slot /root/ (fedora 23, 50GB usati) /btrfssnapshot/ /btrfssnapshot/root/ (for /root/ snapshot) /btrfssnapshot/root/root.1 /btrfssnapshot/root/root.2 /btrfssnapshot/root/root.XYZ subvolume on device HDD "1"

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

> > > At 11/21/2016 08:09 PM, b...@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

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

At 11/21/2016 08:09 PM, b...@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

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

inux-btrfs@vger.kernel.org Subject: Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive > Same problem, this time on a local subvolume. > > kernel-4.8.8-100.fc23.x86_64 > > btrfs-progs v4.8.5 ]zac[ I had three filesystem corruption. T

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

> Chris Murphy Sun, 18 Dec 2016 12:12:42 -0800 > I'd say backup the volume conventionally to get important data > secured. Then use btrfs check --repair to fix the problems with the > file system, and then try the btrfs send receive again. > It most certainly is a bug, but it's not clear to me

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

I'd say backup the volume conventionally to get important data secured. Then use btrfs check --repair to fix the problems with the file system, and then try the btrfs send receive again. It most certainly is a bug, but it's not clear to me what the cause is; other than the kernel isn't handling

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

> Same problem, this time on a local subvolume. > > kernel-4.8.8-100.fc23.x86_64 > > btrfs-progs v4.8.5 ]zac[ I had three filesystem corruption. The point at which the problem it appeared, is similar in all three cases. Subvolume structure and operations sequence: btrfsreceive/

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

> I haven't seen this with 4.7.10. I suggest running 'btrfs check' > (without repair) using a recent btrfs-progs. You can find 4.8.3 in > koji, just download the appropriate rpm, and 'dnf update *rpm' > > As for kernel, Fedora 23 has 4.8.8 in updates (stable) and 4.8.10 is > in updates-testing, I

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

I have reinstalled from scratch my system (for remote receiving of the snapshot). Now it uses the 4.8.8-100.fc23.x86_64 kernel, and now I have a separate partition for '''possible dangerous''' test. I do not remember the exact sequence that caused the corruption of the file system, but now it

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

I haven't seen this with 4.7.10. I suggest running 'btrfs check' (without repair) using a recent btrfs-progs. You can find 4.8.3 in koji, just download the appropriate rpm, and 'dnf update *rpm' As for kernel, Fedora 23 has 4.8.8 in updates (stable) and 4.8.10 is in updates-testing, I suggest

Re: [CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

from /var/log/messages Nov 20 20:04:29 exnetold kernel: Modules linked in: fuse bridge ebtable_filter ebtables tun 8021q bnx2fc cnic uio garp mrp fcoe stp llc libfcoe libfc scsi_transport_fc nvidia_modeset(POE) nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_multiport ip6t_REJECT nf_reject_ipv6

[CORRUPTION FILESYSTEM] Corrupted and unrecoverable file system during the snapshot receive

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