linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Heimpel <broetchenrackete@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Need help recovering broken RAID5 array (parent transid verify failed)
Date: Wed, 20 May 2020 11:56:06 +0000 (UTC)	[thread overview]
Message-ID: <343f7aa9-4cff-45b7-8635-4ca19014c4e5@localhost> (raw)
In-Reply-To: <f6d9ee8a-c0da-4b19-af3a-3c58c9c1478e@localhost>

[-- Attachment #1: Type: text/plain, Size: 9705 bytes --]

Hi again,

I ran find-root and using the first found root (that is not in the superblock) seems to be finding data with btrfs-restore (only did a dry-run, because I don't have the space at the moment to do a full restore). At least I got warnings about folders where it stopped looping and I recognized the folders. It is still not showing any files, but maybe I misunderstood what the dry-run option is suppose to be doing.

Because the generation of the root is higher than expected, I don't know which root is expected to be the best option to choose from. One that is closest to the root the super thinks is the correct one (fe 30122555883520(gen: 116442 level: 0)) or the one with the highest generation (30122107502592(gen: 116502 level: 1))? To be honest I don't think I quite understand generations and levels :)

My plan would be to restore as much as possible and then try to repair the fs, do a scrub and then see if it managed to fix more data and do a backup of it. Than I would recreate the fs from scratch and restore the backup :)

You can find the output of find-root in the txt attached.

Greetings,
Emil

May 16, 2020 03:44:17 Emil Heimpel <broetchenrackete@gmail.com>:

>       Hi, 
>      
>  
>      Thanks for the answer. I attached the output of the commands you requested as a txt file. Unfortunately mounting didn't work, even with the kernel patch and skipbg option. 
>      
>  
>      I will try to find the journalctl from when it happened. 
>      
>  
>      Emil 
>      
>  
>      May 15, 2020 23:46:55 Chris Murphy <lists@colorremedies.com>: 
>      
>  
>       
>      
> 
> >              On Fri, May 15, 2020 at 12:03 AM Emil Heimpel 
> >       
> >      
> >       <broetchenrackete@gmail.com> wrote: 
> >       
> >      
> >        
> >            
> >        
> >       
> > >  
> > >               
> > >              Hi, 
> > >        
> > >       
> > >         
> > >              I hope this is the right place to ask for help. I am unable to mount my BTRFS array and wanted to know, if it is possible to recover (some) data from it. 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            Hi, yes it is! 
> >       
> >      
> >        
> >             
> >             
> >            
> >        
> >       
> > >  
> > >              I have a RAID1-Metadata/RAID5-Data array consisting of 6 drives, 2x8TB, 5TB, 4TB and 2x3TB. It was running fine for the last 3 months. Because I expanded it drive by drive I wanted to do a full balance the other day, when after around 40% completion (ca 1.5 days) I noticed, that one drive was missing from the array (If I remember correctly, it was the 5TB one). I tried to cancel the balance, but even after a few hours it didn't cancel, so I tried to do a reboot. That didn't work either, so I did a hard reset. Probably not the best idea, I know.... 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            The file system should be power fail safe (with some limited data 
> >       
> >      
> >       loss), but the hardware can betray everything. Your configuration is 
> >       
> >      
> >       better due to raid1 metadata. 
> >       
> >      
> >        
> >            
> >        
> >       
> > >  
> > >              After the reboot all drives appeared again but now I can't mount the array anymore, it gives me the following error in dmesg: 
> > >        
> > >       
> > >         
> > >              [  858.554594] BTRFS info (device sdc1): disk space caching is enabled 
> > >        
> > >       
> > >        [  858.554596] BTRFS info (device sdc1): has skinny extents 
> > >        
> > >       
> > >        [  858.556165] BTRFS error (device sdc1): parent transid verify failed on 23219912048640 wanted 116443 found 116484 
> > >        
> > >       
> > >        [  858.556516] BTRFS error (device sdc1): parent transid verify failed on 23219912048640 wanted 116443  found 116484 
> > >        
> > >       
> > >        [  858.556527] BTRFS error (device sdc1): failed to read chunk root 
> > >        
> > >       
> > >        [  858.588332] BTRFS error (device sdc1): open_ctree failed 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            Extent tree is damaged, but it's unexpected that a newer transid is 
> >       
> >      
> >       found than is wanted. Something happened out of order. Both copies. 
> >       
> >      
> >        
> >            What do you get for: 
> >       
> >      
> >       # btrfs rescue super -v /dev/anydevice 
> >       
> >      
> >       # btrfs insp dump-s -fa /dev/anydevice 
> >       
> >      
> >       # btrfs insp dump-t -b 30122546839552 /dev/anydevice 
> >       
> >      
> >       # mount -o ro,nologreplay,degraded /dev/anydevice 
> >       
> >      
> >        
> >             
> >             
> >             
> >            
> >        
> >       
> > >  
> > >              [bluemond@BlueQ btrfslogs]$ sudo btrfs check /dev/sdd1 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            For what it's worth, btrfs check does find all member devices, so you 
> >       
> >      
> >       only have to run check on any one of them. However, scrub is 
> >       
> >      
> >       different, you can run that individually per block device to work 
> >       
> >      
> >       around some performance problems with raid56, when running it on the 
> >       
> >      
> >       volume's mount point. 
> >       
> >      
> >        
> >             
> >            
> >        
> >        
> >       
> > 
> > >                And how can I prevent it from happening again? Would using the new multi-parity raid1 for Metadata help? 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            Difficult to know yet what went wrong. Do you have dmesg/journalctl -k 
> >       
> >      
> >       for the time period the problem drive began all the way to the forced 
> >       
> >      
> >       power off? It might give a hint. Before doing a forced poweroff while 
> >       
> >      
> >       writes are happening it might help to disable the write cache on all 
> >       
> >      
> >       the drives; or alternatively always disable them. 
> >       
> >      
> >        
> >             
> >            
> >        
> >        
> >       
> > 
> > >                I'm running arch on an ssd. 
> > >        
> > >       
> > >        [bluemond@BlueQ btrfslogs]$ uname -a 
> > >        
> > >       
> > >        Linux BlueQ 5.6.12-arch1-1 #1 SMP PREEMPT Sun, 10 May 2020 10:43:42 +0000 x86_64 GNU/Linux 
> > >        
> > >       
> > >         
> > >              [bluemond@BlueQ btrfslogs]$ btrfs --version 
> > >        
> > >       
> > >        btrfs-progs v5.6 
> > >        
> > >       
> > >         
> > >             
> > >         
> > >       
> >  
> >            5.6.1 is current but I don't think there's anything in the minor 
> >       
> >      
> >       update that applies here. 
> >       
> >      
> >        
> >            Post that info and maybe a dev will have time to take a look. If it 
> >       
> >      
> >       does mount ro,degraded, take the chance to update backups, just in 
> >       
> >      
> >       case. Yeah, ~21TB will be really inconvenient to lose. Also, since 
> >       
> >      
> >       it's over the weekend, and there's some time, it might be useful to 
> >       
> >      
> >       have a btrfs image: 
> >       
> >      
> >        
> >            btrfs-image -ss -c9 -t4 /dev/anydevice ~/problemvolume.btrfs.bin 
> >       
> >      
> >        
> >            This file will be roughly 1/2 the size of file system metadata. I 
> >       
> >      
> >       guess you could have around 140G of metadata depending on nodesize 
> >       
> >      
> >       chosen at mkfs time, and how many small files this filesystem has. 
> >       
> >      
> >        
> >            Still another option that might make it possible to mount, if above 
> >       
> >      
> >       doesn't work; build the kernel with this patch 
> >       
> >      
> >       https://patchwork.kernel.org/project/linux-btrfs/list/?series=170715 
> >       
> >      
> >        
> >            Mount using -o ro,nologreplay,rescue=skipbg 
> >       
> >      
> >        
> >            This also doesn't actually fix the problem, it just might make it 
> >       
> >      
> >       possible to mount the file system, mainly for updating backups in case 
> >       
> >      
> >       it's not possible to fix. 
> >       
> >      
> >        
> >             
> >            -- 
> >       
> >      
> >       Chris Murphy 
> >       
> >      
> >        
> >           
> >        
> >      
>  
>     

[-- Attachment #2: btrsf.findroot.txt --]
[-- Type: text/plain, Size: 18992 bytes --]

Superblock thinks the generation is 116443
Superblock thinks the level is 1
Found tree root at 30122565173248 gen 116443 level 1
Well block 30122107502592(gen: 116502 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122107666432(gen: 116501 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122106765312(gen: 116500 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122121658368(gen: 116497 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122102996992(gen: 116496 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122101309440(gen: 116495 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122100391936(gen: 116494 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122099458048(gen: 116493 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122319429632(gen: 116492 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122137387008(gen: 116491 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122497638400(gen: 116490 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122473930752(gen: 116489 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122315579392(gen: 116486 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122315563008(gen: 116486 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122304487424(gen: 116485 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122304471040(gen: 116485 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122298032128(gen: 116479 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468933632(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468917248(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468900864(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468884480(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468868096(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468802560(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468786176(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468769792(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468605952(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468589568(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468376576(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468343808(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468311040(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468294656(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468261888(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468229120(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122468212736(gen: 116469 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122293592064(gen: 116458 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555883520(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555867136(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555850752(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555621376(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555588608(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555555840(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555523072(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122555473920(gen: 116442 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122549657600(gen: 116441 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122546806784(gen: 116438 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122308403200(gen: 116433 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122308386816(gen: 116433 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482024448(gen: 116408 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122481991680(gen: 116408 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122481958912(gen: 116408 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122491805696(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122491789312(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122486235136(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122485547008(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482909184(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482827264(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482810880(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482778112(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482745344(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 30122482401280(gen: 116342 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280847659008(gen: 116336 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280840925184(gen: 116335 level: 1) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280834338816(gen: 116332 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280834289664(gen: 116332 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280831553536(gen: 116332 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280825786368(gen: 116332 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280797081600(gen: 116331 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280796393472(gen: 116331 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280795017216(gen: 116331 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280776388608(gen: 116330 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280757891072(gen: 116330 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019932790784(gen: 116327 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019932774400(gen: 116327 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019893288960(gen: 116327 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019857506304(gen: 116327 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019857113088(gen: 116327 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019888455680(gen: 116326 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 26387051118592(gen: 116326 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 25310236639232(gen: 116326 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 7559563935744(gen: 116326 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 7559367458816(gen: 116325 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6692570562560(gen: 116325 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281085046784(gen: 110860 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281063141376(gen: 110860 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281140408320(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280909410304(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280871923712(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280697090048(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280682033152(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279853658112(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279850364928(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279718981632(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279684329472(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279553667072(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279550570496(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279419121664(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019801653248(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6692393353216(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6692219633664(gen: 110859 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281095565312(gen: 110551 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281039679488(gen: 110468 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019988627456(gen: 110337 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28019975077888(gen: 110337 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280952942592(gen: 109937 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280627884032(gen: 109388 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280627326976(gen: 109388 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281210564608(gen: 109385 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279846973440(gen: 109375 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279843237888(gen: 109375 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280196804608(gen: 108637 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29281185710080(gen: 108633 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280468254720(gen: 108527 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280300072960(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29280017432576(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279680036864(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279552847872(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 4923159674880(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 4923153940480(gen: 108526 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279432982528(gen: 108520 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279380799488(gen: 108520 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279363055616(gen: 108520 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279355617280(gen: 108520 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 29279175802880(gen: 108520 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 5863619493888(gen: 108519 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 26386847678464(gen: 108383 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 26386468356096(gen: 108380 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 2799412903936(gen: 108325 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28020530233344(gen: 108227 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 26386416762880(gen: 108220 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 5863448657920(gen: 107686 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28020194623488(gen: 107672 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075667271680(gen: 107620 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28020127137792(gen: 107614 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 28020388724736(gen: 107386 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24309878816768(gen: 107376 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6691901718528(gen: 106867 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24310098575360(gen: 106811 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 26387216056320(gen: 103210 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 23220080590848(gen: 102044 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24310357229568(gen: 100795 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24310530441216(gen: 96307 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24310298656768(gen: 96271 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 24310293741568(gen: 96271 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 23237383012352(gen: 92298 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 23220814233600(gen: 92237 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 23220295778304(gen: 92219 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6692060151808(gen: 91345 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 22279392444416(gen: 89503 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6691836723200(gen: 2484 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 6691836674048(gen: 2484 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075344343040(gen: 505 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075872677888(gen: 429 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075771080704(gen: 403 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075652542464(gen: 380 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1
Well block 1075554172928(gen: 365 level: 0) seems good, but generation/level doesn't match, want gen: 116443 level: 1

  reply	other threads:[~2020-05-20 11:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  6:03 Need help recovering broken RAID5 array (parent transid verify failed) Emil Heimpel
2020-05-15 21:46 ` Chris Murphy
2020-05-16  1:44   ` Emil Heimpel
2020-05-20 11:56     ` Emil Heimpel [this message]
2020-05-20 19:01       ` Chris Murphy
     [not found]         ` <21913a92-5059-405f-b2d4-91e785ab77bd@gmail.com>
2020-06-04 22:55           ` Emil Heimpel
2020-09-28 13:04             ` Dan van der Ster
2020-10-01  4:49             ` Zygo Blaxell

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=343f7aa9-4cff-45b7-8635-4ca19014c4e5@localhost \
    --to=broetchenrackete@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).