Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Mon, 4 Apr 2016 17:09:14 -0600 schrieb Chris Murphy : > > Why couldn't/shouldn't I remove snapshots before detaching the seed > > device? I want to keep them on the seed but they are useless to me > > on the sprout. > > You can remove snapshots before or after

Re: btrfsck: backpointer mismatch (and multiple other errors)

Kai Krakow posted on Mon, 04 Apr 2016 21:26:28 +0200 as excerpted: > I'll go test the soon-to-die SSD as soon as it replaced. I think it's > still far from failing with bitrot. It was overprovisioned by 30% most > of the time, with the spare space trimmed. Same here, FWIW. In fact, I had

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Mon, Apr 4, 2016 at 2:50 PM, Kai Krakow wrote: >> Anyway the 2nd 4 is not possible. The seed is ro by definition so you >> can't remove snapshots from the seed. If you remove them from the >> mounted rw sprout volume, they're removed from the sprout, not the >> seed. If

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Mon, 4 Apr 2016 22:50:18 +0200 schrieb Kai Krakow : > Am Mon, 4 Apr 2016 13:57:50 -0600 > schrieb Chris Murphy : > > > On Mon, Apr 4, 2016 at 1:36 PM, Kai Krakow > > wrote: > > > > > > > [...] > [...] > > > >

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Mon, 4 Apr 2016 13:57:50 -0600 schrieb Chris Murphy : > On Mon, Apr 4, 2016 at 1:36 PM, Kai Krakow > wrote: > > > > [...] > >> > >> ? > > > > In the following sense: I should disable the automounter and backup > > job for the seed device

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Mon, Apr 4, 2016 at 1:36 PM, Kai Krakow wrote: > >> > I guess the >> > seed source cannot be mounted or modified... >> >> ? > > In the following sense: I should disable the automounter and backup job > for the seed device while I let my data migrate back to main storage

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Sun, 3 Apr 2016 18:51:07 -0600 schrieb Chris Murphy : > > BTW: Is it possible to use my backup drive (it's btrfs single-data > > dup-metadata, single device) as a seed device for my newly created > > btrfs pool (raid0-data, raid1-metadata, three devices)? > > Yes. >

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Mon, 4 Apr 2016 04:34:54 + (UTC) schrieb Duncan <1i5t5.dun...@cox.net>: > Meanwhile, putting bcache into write-around mode, so it makes no > further changes to the ssd and only uses it for reads, is probably > wise, and should help limit further damage. Tho if in that mode > bcache still

Re: btrfsck: backpointer mismatch (and multiple other errors)

Kai Krakow posted on Mon, 04 Apr 2016 00:19:25 +0200 as excerpted: > The corruptions seem to be different by the following observation: > > While the VDI file was corrupted over and over again with a csum error, > I could simply remove it and restore from backup. The last thing I did > was

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Sun, Apr 3, 2016 at 4:19 PM, Kai Krakow wrote: > BTW: Is it possible to use my backup drive (it's btrfs single-data > dup-metadata, single device) as a seed device for my newly created > btrfs pool (raid0-data, raid1-metadata, three devices)? Yes. I just tried doing

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Sun, 3 Apr 2016 05:06:19 + (UTC) schrieb Duncan <1i5t5.dun...@cox.net>: > Kai Krakow posted on Sun, 03 Apr 2016 06:02:02 +0200 as excerpted: > > > No, other files are affected, too. And it looks like those files are > > easily affected even when removed and recreated from whatever backup

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Sat, Apr 2, 2016 at 10:02 PM, Kai Krakow wrote: > Am Sat, 2 Apr 2016 18:14:17 -0600 > Also I think, having options nossd+autodefrag+lzo shouldn't be an > exotic or unsupported option. Having this on top of bcache should just > work. I'm not suggesting it shouldn't work.

Re: btrfsck: backpointer mismatch (and multiple other errors)

Kai Krakow posted on Sun, 03 Apr 2016 06:02:02 +0200 as excerpted: > No, other files are affected, too. And it looks like those files are > easily affected even when removed and recreated from whatever backup > source. I've seen you say that several times now, I think. But none of those times

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Sat, 2 Apr 2016 18:14:17 -0600 schrieb Chris Murphy : > On Sat, Apr 2, 2016 at 2:16 PM, Kai Krakow > wrote: > > > I'll go checking the RAM for problems - tho that would be the first > > time in twenty years that a RAM module hadn't errors from

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Sat, Apr 2, 2016 at 2:16 PM, Kai Krakow wrote: > I'll go checking the RAM for problems - tho that would be the first > time in twenty years that a RAM module hadn't errors from the > beginning. Well, you'll never know. But I expect no error since usually > this would

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Sat, 2 Apr 2016 19:17:55 +0200 schrieb Henk Slager : > On Sat, Apr 2, 2016 at 11:00 AM, Kai Krakow > wrote: > > Am Fri, 1 Apr 2016 01:27:21 +0200 > > schrieb Henk Slager : > > > >> It is not clear to me what 'Gentoo patch-set r1' is

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Sat, Apr 2, 2016 at 11:00 AM, Kai Krakow wrote: > Am Fri, 1 Apr 2016 01:27:21 +0200 > schrieb Henk Slager : > >> It is not clear to me what 'Gentoo patch-set r1' is and does. So just >> boot a vanilla v4.5 kernel from kernel.org and see if you get csum

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Fri, 1 Apr 2016 01:27:21 +0200 schrieb Henk Slager : > It is not clear to me what 'Gentoo patch-set r1' is and does. So just > boot a vanilla v4.5 kernel from kernel.org and see if you get csum > errors in dmesg. It is the gentoo patchset, I don't think anything there

Re: btrfsck: backpointer mismatch (and multiple other errors)

Am Fri, 1 Apr 2016 09:10:44 +0800 schrieb Qu Wenruo : > The real problem is, the extent has mismatched reference. > Normally it can fixed by --init-extent-tree option, but it normally > means bigger problem, especially it has already caused kernel > delayed-ref problem.

Re: btrfsck: backpointer mismatch (and multiple other errors)

Henk Slager wrote on 2016/04/01 01:27 +0200: On Thu, Mar 31, 2016 at 10:44 PM, Kai Krakow wrote: Hello! I already reported this in another thread but it was a bit confusing by intermixing multiple volumes. So let's start a new thread: Since one of the last kernel

Re: btrfsck: backpointer mismatch (and multiple other errors)

On Thu, Mar 31, 2016 at 10:44 PM, Kai Krakow wrote: > Hello! > > I already reported this in another thread but it was a bit confusing by > intermixing multiple volumes. So let's start a new thread: > > Since one of the last kernel upgrades, I'm experiencing one VDI file >

btrfsck: backpointer mismatch (and multiple other errors)

Hello! I already reported this in another thread but it was a bit confusing by intermixing multiple volumes. So let's start a new thread: Since one of the last kernel upgrades, I'm experiencing one VDI file (containing a NTFS image with Windows 7) getting damaged when running the machine in