btrfs check bug

2017-04-18 Thread Jan Koester

Hi,

i have to try to create a new extent-tree after checksum error not solveable 
with srub or init-csum-tree.
Now i got this failure output from btrfs --repair:
 
ERROR: errors found in extent allocation tree or chunk allocation
Fixed 0 roots.
checking free space cache
checking fs roots
root 5 missing its root dir, recreating
btrfs unable to find ref byte nr 2279425310720 parent 0 root 5  owner 3 offset 0
btrfs unable to find ref byte nr 2279422181376 parent 0 root 5  owner 2 offset 1
btrfs unable to find ref byte nr 2279422672896 parent 0 root 5  owner 1 offset 1
btrfs unable to find ref byte nr 2279413121024 parent 0 root 5  owner 0 offset 1
cmds-check.c:3370: check_inode_recs: BUG_ON `ret` triggered, value -17
btrfs(+0x50788)[0x5565c775b788]
btrfs(+0x507db)[0x5565c775b7db]
btrfs(+0x598e6)[0x5565c77648e6]
btrfs(cmd_check+0x2bd4)[0x5565c7770185]
btrfs(main+0x8b)[0x5565c771c0f5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f76045232b1]
btrfs(_start+0x2a)[0x5565c771bd7a]
enabling repair mode
Checking filesystem on /dev/disk/by-label/home
UUID: 74454fdd-035b-4a3d-98ec-e38d3e7bcd6b
cache and super generation don't match, space cache will be invalidated
Failed to find [2278878576640, 168, 16384]
Failed to find [2278878593024, 168, 16384]
Failed to find [2278878609408, 168, 16384]
Failed to find [2278878625792, 168, 16384]
--
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: mounting failed any file on my filesystem

2017-01-01 Thread Jan Koester
On Samstag, 31. Dezember 2016 05:05:03 CET Duncan wrote:
> Jan Koester posted on Fri, 30 Dec 2016 13:17:37 +0100 as excerpted:
> > sudo btrfs filesystem df /mnt
> > Data, RAID6: total=1.22TiB, used=0.00B
> > System, RAID6: total=96.00MiB, used=0.00B
> > Metadata, RAID6: total=8.25GiB, used=80.00KiB
> > GlobalReserve, single: total=512.00MiB, used=8.00KiB
> 
> Expanding on what I already mentioned in passing (hoping it wasn't the
> case), raid56 mode (so including your raid6) remains quite unstable, with
> known problems that make it unsuitable for the sort of purposes people
> normally run parity-raid for.  So it's actively negatively recommended
> unless you're running it for the specific purpose of trying to help the
> devs work out the problems with it, using only throw-away-value test data
> in case those problems eat it, which unfortunately they have a
> significantly real chance of doing, with raid56 at this point.
> 
> So you need to get off of it ASAP, and hope any data that wasn't already
> throw-away-value, doesn't end up being thrown away anyway, in the process.
> 
> Unfortunately, as I said in the earlier post, I'm just a user, tho a list
> regular, myself, not a dev.  And I've been staying well away from raid56
> /because/ of these problems (as well as because it didn't fit my use-case
> in the first place), so other than noting the severity of the issues,
> I've not really been paying attention to the various threads with people
> trying to fix the problems and save at least some of their raid56 stored
> data.
> 
> So if you want to try to save the data, you'll need help from a dev or
> higher level expert, or failing that, at least to examine the last couple
> 2-3 months worth of list threads and find the raid56 ones with methods to
> try to save what can be saved, and possibly to patch at least some of the
> problems in ordered to not make the problem worse while you're doing so.
> 
> But it's going to require some reasonable technical know-how to try to do
> that, as well as the time and hassle, so honestly, unless that data's
> /really/ worth it, it may be better to simply cut and run, doing a fresh
> mkfs and being done with btrfs raid56 for now, without spending more time
> on it, only to find you can't save much anyway.  Tho if it's worth it to
> you, you may be able to save much of it, but you could spend a month's
> man-hours doing it too and possibly still come up empty.  Plus be
> careful, because stuff like scrub that would normally help, can make the
> problem much much worse in the case of raid56 ATM.  Yes, the problems
> with it ATM *are* that bad.  Unfortunately.  There's actually talk of
> scrapping the code (almost?) entirely and starting over again, as there's
> a real question as to whether it can even be properly fixed, tho I'm not
> sure it will come to that.

I have backup of this data i wan't to help the Dev's too fix this bug because i 
have enough hard drives.I can also give remote access to show what happend 
with the filesystem or other thins that could he to fix this bug. I see at the 
moment much things happened on the raid56 code.


--
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: mounting failed any file on my filesystem

2016-12-30 Thread Jan Koester
On Donnerstag, 29. Dezember 2016 22:31:29 CET Duncan wrote:
> Jan Koester posted on Thu, 29 Dec 2016 20:05:35 +0100 as excerpted:
> > Hi,
> > 
> > i have problem with filesystem if my system crashed i have made been
> > hard reset of the system after my Filesystem was crashed. I have already
> > tried to repair without success you can see it on log file. It's seem
> > one corrupted block brings complete filesystem to crashing.
> > 
> > Have anybody idea what happened with my filesystem ?
> > 
> > dmesg if open file:
> > [29450.404327] WARNING: CPU: 5 PID: 16161 at
> > /build/linux-lIgGMF/linux-4.8.11/ fs/btrfs/extent-tree.c:6945
> > __btrfs_free_extent.isra.71+0x8e2/0xd60 [btrfs]
> 
> First a disclaimer.  I'm a btrfs user and list regular, not a dev.  As
> such I don't really read call traces much beyond checking the kernel
> version, and don't do code.  It's likely that you will get a more
> authoritative reply from someone who does, and it should take precedence,
> but in the mean time, I can try to deal with the preliminaries.
> 
> Kernel 4.8.11, good.  But you run btrfs check below, and we don't have
> the version of your btrfs-progs userspace.  Please report that too.
> 
> > btrfs output:
> > root@dibsi:/home/jan# btrfs check /dev/disk/by-uuid/
> > 73d4dc77-6ff3-412f-9b0a-0d11458faf32
> 
> Note that btrfs check is read-only by default.  It will report what it
> thinks are errors, but won't attempt to fix them unless you add various
> options (such as --repair) to tell it to do so.  This is by design and is
> very important, as attempting to repair problems that it doesn't properly
> understand could make the problems worse instead of better.  So even tho
> the above command will only report what it sees as problems, not attempt
> to fix them, you did the right thing by running check without --repair
> first, and posting the results here for an expert to look at and tell you
> whether to try --repair, or what else to try instead.
> 
> > Checking filesystem on
> > /dev/disk/by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32
> > UUID: 73d4dc77-6ff3-412f-9b0a-0d11458faf32
> > checking extents
> > parent transid verify failed on 2280458502144 wanted 861168
> > found 860380
> > parent transid verify failed on 2280458502144 wanted 861168
> > found 860380
> > checksum verify failed on 2280458502144 found FC3DF84D
> > wanted 2164EB93
> > checksum verify failed on 2280458502144 found FC3DF84D
> > wanted 2164EB93
> > bytenr mismatch, want=2280458502144, have=15938383240448
> 
> [...]
> 
> Some other information that we normally ask for includes the output from
> a few other btrfs commands.
> 
> It's unclear from your report if the filesystem will mount at all.  The
> subject says mount failed, but then it mentions any file on the
> filesystem, which seems to imply that you could mount, but that any file
> you attempted to actually access after mounting crashes the system with
> the trace you posted, so I'm not sure if you can actually mount the
> filesystem at all.
> 
> If you can't mount the filesystem, at least try to post the output from...
> 
> btrfs filesystem show
> 
> If you can mount the filesystem, then the much more detailed...
> 
> btrfs filesystem usage
> 
> ... if your btrfs-progs is new enough, or...
> 
> btrfs filesystem df
> 
> ... if btrfs-progs is too old to have the usage command.
> 
> Also, if it's not clear from the output of the commands above (usage by
> itself, or show plus df, should answer most of the below, but show alone
> only provides some of the information), tell us a bit more about the
> filesystem in question:
> 
> Single device (like traditional filesystems) or multiple device?  If
> multiple device, what raid levels if you know them, or did you just go
> with the defaults.  If single device, again, defaults, or did you specify
> single or dup, particularly for metadata.
> 
> Also, how big was the filesystem and how close to full?  And was it on
> ssd, spinning rust, or on top of something virtual (like a VM image
> existing as a file on the host, or lvm, or mdraid, etc)?
> 
> 
> Meanwhile, if you can mount, the first thing I'd try is btrfs scrub
> (unless you were running btrfs raid56 mode, which makes things far more
> complex as it's not stable yet and isn't recommended except for testing
> with data you can afford to lose).  Often, a scrub can fix much of the
> damage of a crash if you were running raid1 mode (multi-device metadata
> default), raid10, or dup (single device metadata default, except on ssd),
> as those have a second checksummed copy that will often be correct that
> scrub can use t

mounting failed any file on my filesystem

2016-12-29 Thread Jan Koester
Hi,

i have problem with filesystem if my system crashed i have made been hard reset 
of the system after my Filesystem was crashed. I have already tried to repair 
without success you can see it on log file. It's seem one corrupted block 
brings complete filesystem to crashing.

Have anybody idea what happened with my filesystem ?

dmesg if open file:
[29450.404327] WARNING: CPU: 5 PID: 16161 at /build/linux-lIgGMF/linux-4.8.11/
fs/btrfs/extent-tree.c:6945 __btrfs_free_extent.isra.71+0x8e2/0xd60 [btrfs]
[29450.404331] Modules linked in: snd_usb_audio snd_usbmidi_lib snd_rawmidi 
snd_seq_device nfnetlink_queue nfnetlink_log nfnetlink cfg80211 bnep 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bluetooth rfkill 
binfmt_misc ext4 crc16 jbd2 fscrypto ecb mbcache btrfs xor raid6_pq kvm_amd 
kvm amdkfd irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel radeon 
snd_hda_codec_realtek snd_hda_codec_generic sr_mod cdrom pcspkr serio_raw 
snd_hda_codec_hdmi fam15h_power k10temp evdev snd_hda_intel ttm snd_hda_codec 
drm_kms_helper snd_hda_core snd_hwdep snd_pcm drm snd_timer snd soundcore 
i2c_algo_bit sg sp5100_tco nuvoton_cir shpchp rc_core acpi_cpufreq tpm_tis 
tpm_tis_core tpm button cuse fuse parport_pc ppdev lp parport ip_tables
[29450.404512]  x_tables autofs4 xfs libcrc32c crc32c_generic ata_generic 
hid_generic usbhid hid sd_mod uas usb_storage ohci_pci crc32c_intel 
aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse 
e1000e xhci_pci r8169 xhci_hcd ptp ahci mii pps_core pata_atiixp libahci 
ohci_hcd libata ehci_pci ehci_hcd usbcore scsi_mod i2c_piix4 usb_common fjes
[29450.404543] CPU: 5 PID: 16161 Comm: kworker/u12:3 Tainted: GW  OE   
4.8.0-2-amd64 #1 Debian 4.8.11-1
[29450.404544] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./
970 Extreme3, BIOS P1.80 07/31/2013
[29450.404579] Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs]
[29450.404581]  0286 0bc03c37 93d269f5 

[29450.404586]   93a7c16e fffe 
00dd8f8a8000
[29450.404590]   91c65d625000 91c4eac5c000 
91c4e7c09690
[29450.404594] Call Trace:
[29450.404599]  [] ? dump_stack+0x5c/0x77
[29450.404603]  [] ? __warn+0xbe/0xe0
[29450.404630]  [] ? __btrfs_free_extent.isra.71+0x8e2/0xd60 
[btrfs]
[29450.404660]  [] ? block_group_cache_tree_search+0x21/0xd0 
[btrfs]
[29450.404690]  [] ? update_block_group.isra.70+0x133/0x420 
[btrfs]
[29450.404699]  [] ? __set_page_dirty_nobuffers+0xef/0x140
[29450.404736]  [] ? btrfs_merge_delayed_refs+0x69/0x580 
[btrfs]
[29450.404767]  [] ? __btrfs_run_delayed_refs+0xadc/0x1240 
[btrfs]
[29450.404801]  [] ? btrfs_run_delayed_refs+0x8e/0x2a0 
[btrfs]
[29450.404834]  [] ? delayed_ref_async_start+0x89/0xa0 
[btrfs]
[29450.404871]  [] ? btrfs_scrubparity_helper+0xd1/0x2d0 
[btrfs]
[29450.404879]  [] ? process_one_work+0x160/0x410
[29450.404886]  [] ? worker_thread+0x4d/0x480
[29450.404892]  [] ? process_one_work+0x410/0x410
[29450.404899]  [] ? kthread+0xcd/0xf0
[29450.404906]  [] ? ret_from_fork+0x1f/0x40
[29450.404913]  [] ? kthread_create_on_node+0x190/0x190
[29450.404919] ---[ end trace 9627fcfceb44da0b ]---
[29450.404926] BTRFS info (device sdd): leaf 950359678976 total ptrs 67 free 
space 442
[29450.404934]  item 0 key (503649468416 192 1107296256) itemoff 3971 itemsize 
24
[29450.404940]  block group used 36864
[29450.404947]  item 1 key (503649538048 169 0) itemoff 3938 itemsize 33
[29450.404952]  extent refs 1 gen 861177 flags 2
[29450.404959]  tree block backref root 2
[29450.404965]  item 2 key (503649550336 169 1) itemoff 3905 itemsize 33
[29450.404971]  extent refs 1 gen 861177 flags 2
[29450.404977]  tree block backref root 2
[29450.404984]  item 3 key (503649566720 169 0) itemoff 3872 itemsize 33
[29450.404991]  extent refs 1 gen 861177 flags 2
[29450.404996]  tree block backref root 2
[29450.405001]  item 4 key (503649570816 169 0) itemoff 3839 itemsize 33
[29450.405007]  extent refs 1 gen 861177 flags 2
[29450.405012]  tree block backref root 2
[29450.405019]  item 5 key (503649607680 169 0) itemoff 3806 itemsize 33
[29450.405025]  extent refs 1 gen 861177 flags 2
[29450.405028]  tree block backref root 2
[29450.405030]  item 6 key (503649628160 169 0) itemoff 3773 itemsize 33
[29450.405031]  extent refs 1 gen 861177 flags 2
[29450.405032]  tree block backref root 2
[29450.405034]  item 7 key (503649636352 169 0) itemoff 3740 itemsize 33
[29450.405036]  extent refs 1 gen 861177 flags 2
[29450.405037]  tree block backref root 2
[29450.405039]  item 8 key (503649669120 169 1) itemoff 3707 itemsize 33
[29450.405040]  extent refs 1 gen 861177 flags 2
[29450.405041]  tree block backref root 1
[29450.405043]  item 9 key 

chunk recover segfault

2016-11-12 Thread Jan Koester
Hi,

got segault if i run rescue chunk-recover.

My Kernel:
Linux dibsi 4.9.0-040900rc2-generic #201610232131 SMP Mon Oct 24 01:32:49 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

btrfs Progs:
btrfs-progs v4.8.3

gdb ouput btrfs rescue chunk-recover:
Starting program: /home/jan/btrfs-progs/btrfs rescue chunk-recover /dev/disk/
by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x76f6e700 (LWP 29108)]
[New Thread 0x7fffe700 (LWP 29109)]
[New Thread 0x7676d700 (LWP 29110)]
[New Thread 0x75f6c700 (LWP 29111)]
[New Thread 0x7576b700 (LWP 29112)]
Scanning: 938721280 in dev0, 959299584 in dev1, 845529088 in dev2, 913293312 
in dev3, 962314240 in dev4
Thread 6 "btrfs" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7576b700 (LWP 29112)]
btrfs_new_chunk_record (leaf=leaf@entry=0x7fffd80008c0, 
key=key@entry=0x7576ac90, slot=slot@entry=11)
at cmds-check.c:5126
5126rec->stripes[i].devid =

dmesg output:
btrfs[29091]: segfault at 7f229c022000 ip 00427d41 sp 7f22ab7fdc10 
error 4 in btrfs[40+a1000]
--
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: mount error raid6

2016-10-28 Thread Jan Koester
On Sonntag, 25. September 2016 11:25:40 CEST you wrote:
> Hi,
> 
> i got some errors in dmesg if i want to mount my Filesystem,
> 
> uname -a:
> Linux dibsi 4.8.0-040800rc7-generic #201609182130 SMP Mon Sep 19 01:32:13
> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> 
> dmesg:
> [   71.599464] BTRFS warning (device sde): 'recovery' is deprecated, use
> 'usebackuproot' instead
> [   71.599469] BTRFS info (device sde): trying to use backup root at mount
> time
> [   71.599477] BTRFS info (device sde): disabling disk space caching
> [   71.599487] BTRFS info (device sde): has skinny extents
> [   71.654586] BTRFS error (device sde): parent transid verify failed on
> 2280458645504 wanted 861168 found 860380
> [   71.703142] BTRFS info (device sde): bdev /dev/sda errs: wr 111, rd
> 124642, flush 0, corrupt 0, gen 0
> [   71.752921] BTRFS error (device sde): parent transid verify failed on
> 2280389693440 wanted 861168 found 860380
> [   71.772571] BTRFS error (device sde): parent transid verify failed on
> 2280389709824 wanted 861168 found 860380
> [   71.785304] BTRFS info (device sde): checking UUID tree
> [   71.853116] BTRFS error (device sde): parent transid verify failed on
> 2280458502144 wanted 861168 found 860380
> [   71.868238] BTRFS error (device sde): parent transid verify failed on
> 2280458506240 wanted 861168 found 860380
> [   71.868488] BTRFS error (device sde): parent transid verify failed on
> 2280458510336 wanted 861168 found 860380
> [   71.868977] BTRFS error (device sde): parent transid verify failed on
> 2280458620928 wanted 861168 found 860380
> [   71.869262] BTRFS error (device sde): parent transid verify failed on
> 2280458625024 wanted 861168 found 860380
> [   71.881341] BTRFS error (device sde): parent transid verify failed on
> 2280458629120 wanted 861168 found 860380
> [   71.926156] BTRFS error (device sde): parent transid verify failed on
> 2280458633216 wanted 861168 found 860380
> [  101.960210] [ cut here ]
> [  101.960277] WARNING: CPU: 0 PID: 2850 at /home/kernel/COD/linux/fs/btrfs/
> extent-tree.c:6948 __btrfs_free_extent.isra.71+0x85a/0xd40 [btrfs] [ 
> 101.960293] Modules linked in: binfmt_misc crc32c_generic btrfs xor
> raid6_pq kvm_amd kvm irqbypass snd_hda_codec_hdmi serio_raw snd_hda_intel
> snd_hda_codec k10temp snd_usb_audio snd_hda_core joydev snd_usbmidi_lib
> snd_seq_midi snd_seq_midi_event snd_hwdep snd_ctxfi snd_rawmidi snd_pcm
> snd_seq snd_seq_device i2c_piix4 snd_timer snd tpm_infineon sg soundcore
> evdev shpchp acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc ppdev sunrpc
> lp parport autofs4 ext4 crc16 jbd2 fscrypto mbcache sd_mod hid_generic
> usbhid hid ohci_pci amdkfd radeon i2c_algo_bit ttm ahci drm_kms_helper
> ohci_hcd xhci_pci libahci syscopyarea ehci_pci xhci_hcd sysfillrect libata
> ehci_hcd sysimgblt fb_sys_fops e1000e usbcore drm scsi_mod r8169 ptp mii
> pps_core usb_common wmi fjes button
> [  101.960395] CPU: 0 PID: 2850 Comm: btrfs-transacti Not tainted
> 4.8.0-040800rc7-generic #201609182130
> [  101.960397] Hardware name: Gigabyte Technology Co., Ltd. GA-970A-D3/
> GA-970A-D3, BIOS F12 09/03/2013
> [  101.960402]  00200286 198bae94 9b53fba4
> 
> [  101.960409]   9b27f6ae 00df39b62000
> 883781532d90
> [  101.960415]  fffe 88376bfd2140 8837c393a000
> 
> [  101.960421] Call Trace:
> [  101.960431]  [] ? dump_stack+0x5c/0x78
> [  101.960438]  [] ? __warn+0xbe/0xe0
> [  101.960484]  [] ?
> __btrfs_free_extent.isra.71+0x85a/0xd40 [btrfs]
> [  101.960527]  [] ? btrfs_previous_extent_item+0xe0/0x100
> [btrfs]
> [  101.960570]  [] ?
> update_block_group.isra.70+0x133/0x460 [btrfs]
> [  101.960577]  [] ? __set_page_dirty_nobuffers+0xec/0x140
> [  101.960621]  [] ?
> __btrfs_run_delayed_refs+0x4f3/0x13d0 [btrfs]
> [  101.960668]  [] ? btrfs_run_delayed_refs+0x9a/0x2b0
> [btrfs]
> [  101.960673]  [] ? sched_clock+0x5/0x10
> [  101.960723]  [] ? btrfs_commit_transaction+0x50/0xa60
> [btrfs]
> [  101.960771]  [] ? start_transaction+0x8f/0x4c0 [btrfs]
> [  101.960819]  [] ? transaction_kthread+0x1e9/0x200
> [btrfs] [  101.960866]  [] ?
> btrfs_cleanup_transaction+0x5c0/0x5c0 [btrfs]
> [  101.960872]  [] ? kthread+0xcd/0xf0
> [  101.960877]  [] ? __switch_to+0x2c1/0x7a0
> [  101.960884]  [] ? ret_from_fork+0x1f/0x40
> [  101.960890]  [] ? kthread_create_on_node+0x1a0/0x1a0
> [  101.960893] ---[ end trace 413d8788543e689c ]---
> [  101.960900] BTRFS info (device sde): leaf 950359654400 total ptrs 56 free
> space 945
> [  101.960904]  item 0 key (503649468416 168 4096) itemoff 3944 itemsize 51
> [  101.960908]  extent refs 1 gen 861173 flags 2
> [  101.960911]  tree block key (0 0 0) level 0
> [  101.960912]  tree block backref root 7
> [  101.960916]  item 1 key (503649468416 192 1107296256) itemoff 3920
> itemsize 24
> [  101.960918]  block group used 45056
> [  101.960921]  item 2 key 

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester
checksum verify failed on 503649476608 found F4F3F1B1 wanted 1C93F3D7
checksum verify failed on 503649476608 found F4F3F1B1 wanted 1C93F3D7
bytenr mismatch, want=503649476608, have=372927881216
parent transid verify failed on 503649480704 wanted 2486 found 861173
parent transid verify failed on 503649480704 wanted 2486 found 861173
checksum verify failed on 503649480704 found 8FAAA22D wanted A8B4E15D
bytenr mismatch, want=503649480704, have=503649415168
parent transid verify failed on 503649484800 wanted 141269 found 861172
parent transid verify failed on 503649484800 wanted 141269 found 861172
checksum verify failed on 503649484800 found 44F98D19 wanted 82B3BBC8
checksum verify failed on 503649484800 found 44F98D19 wanted 82B3BBC8
bytenr mismatch, want=503649484800, have=372927880448
parent transid verify failed on 503649505280 wanted 2486 found 861173
parent transid verify failed on 503649505280 wanted 2486 found 861173
checksum verify failed on 503649505280 found 84B91D35 wanted 1356A853
checksum verify failed on 503649505280 found 84B91D35 wanted 1356A853
bytenr mismatch, want=503649505280, have=372927878912
parent transid verify failed on 503649509376 wanted 2486 found 861169
parent transid verify failed on 503649509376 wanted 2486 found 861169
checksum verify failed on 503649509376 found B861BAA7 wanted DED915CC
parent transid verify failed on 503649509376 wanted 2486 found 861169
Ignoring transid failure
bad block 503649509376
Errors found in extent allocation tree or chunk allocation
parent transid verify failed on 2280458502144 wanted 861168 found 860380
parent transid verify failed on 2280458502144 wanted 861168 found 860380
checksum verify failed on 2280458502144 found FC3DF84D wanted 2164EB93
checksum verify failed on 2280458502144 found FC3DF84D wanted 2164EB93
bytenr mismatch, want=2280458502144, have=15938383240448


Am 10.09.2016 um 13:55 schrieb Jan Koester:

Hi,

i have now installed kernel 4.8-rc5 now i got this output when i
starting scrub. My problem is that i can see all files on my Filesystem
but can't access them.

[43176.787859] [ cut here ]
[43176.787926] WARNING: CPU: 1 PID: 19517 at
/home/kernel/COD/linux/fs/btrfs/extent-tree.c:6947
__btrfs_free_extent.isra.71+0x85a/0xd40 [btrfs]
[43176.787928] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs
vfat msdos fat jfs xfs libcrc32c dm_mod binfmt_misc crc32c_generic btrfs
xor raid6_pq kvm_amd kvm irqbypass serio_raw k10temp snd_hda_codec_hdmi
joydev snd_hda_intel snd_hda_codec snd_hda_core snd_usb_audio snd_ctxfi
snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event
snd_rawmidi snd_seq sg snd_seq_device i2c_piix4 snd_timer snd soundcore
tpm_infineon evdev acpi_cpufreq shpchp tpm_tis tpm_tis_core tpm
parport_pc ppdev sunrpc lp parport autofs4 ext4 crc16 jbd2 fscrypto
mbcache sd_mod hid_generic usbhid hid ohci_pci amdkfd radeon
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt
fb_sys_fops drm xhci_pci xhci_hcd ahci libahci ohci_hcd ehci_pci
ehci_hcd libata e1000e usbcore scsi_mod r8169 ptp usb_common
[43176.788305]  pps_core mii fjes wmi button
[43176.788317] CPU: 1 PID: 19517 Comm: kworker/u16:4 Tainted: GW
   4.8.0-040800rc5-generic #201609041832
[43176.788319] Hardware name: Gigabyte Technology Co., Ltd.
GA-970A-D3/GA-970A-D3, BIOS F12 09/03/2013
[43176.788377] Workqueue: btrfs-extent-refs btrfs_extent_refs_helper
[btrfs]
[43176.788382]  0286 1d97bfa2 a5141064

[43176.788389]   a4e7f6ee 00ddc9d93000
976cd9b635b0
[43176.788395]  fffe 976cf93d5be0 976da1478000

[43176.788401] Call Trace:
[43176.788410]  [] ? dump_stack+0x5c/0x78
[43176.788417]  [] ? __warn+0xbe/0xe0
[43176.788461]  [] ?
__btrfs_free_extent.isra.71+0x85a/0xd40 [btrfs]
[43176.788513]  [] ?
btrfs_merge_delayed_refs+0x69/0x570 [btrfs]
[43176.788557]  [] ?
__btrfs_run_delayed_refs+0xb43/0x13d0 [btrfs]
[43176.788564]  [] ? kmem_cache_alloc+0xb7/0x510
[43176.788609]  [] ? btrfs_run_delayed_refs+0x9a/0x2b0
[btrfs]
[43176.788654]  [] ? delayed_ref_async_start+0x89/0xa0
[btrfs]
[43176.788706]  [] ?
btrfs_scrubparity_helper+0xca/0x380 [btrfs]
[43176.788712]  [] ? process_one_work+0x184/0x4b0
[43176.788716]  [] ? worker_thread+0x4d/0x480
[43176.788721]  [] ? __schedule+0x261/0x720
[43176.788725]  [] ? process_one_work+0x4b0/0x4b0
[43176.788730]  [] ? kthread+0xcd/0xf0
[43176.788735]  [] ? __switch_to+0x2c1/0x7a0
[43176.788741]  [] ? ret_from_fork+0x1f/0x40
[43176.788747]  [] ? kthread_create_on_node+0x1a0/0x1a0
[43176.788750] ---[ end trace 18d7bec13eeb81e1 ]---
[43176.788757] BTRFS info (device sde): leaf 950359658496 total ptrs 56
free space 711
[43176.788761]  item 0 key (503649468416 168 4096) itemoff 3944 itemsize 51
[43176.788764]  extent refs 1 gen 861173 flags 2
[43176.788767]  tree block key (0 0 0) level 0
[43176.788778]  tree block backref root 7
[43176.788789]  item 1 key

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester

[43176.789311]  block group used 0
[43176.789314]  item 37 key (994550808576 192 3221225472) itemoff 2543 
itemsize 24

[43176.789315]  block group used 0
[43176.789319]  item 38 key (997772034048 192 3221225472) itemoff 2519 
itemsize 24

[43176.789320]  block group used 0
[43176.789323]  item 39 key (1000993259520 192 3221225472) itemoff 2495 
itemsize 24

[43176.789324]  block group used 0
[43176.789327]  item 40 key (1004214484992 192 3221225472) itemoff 2471 
itemsize 24

[43176.789329]  block group used 0
[43176.789332]  item 41 key (1007435710464 192 3221225472) itemoff 2447 
itemsize 24

[43176.789333]  block group used 0
[43176.789336]  item 42 key (1010656935936 192 3221225472) itemoff 2423 
itemsize 24

[43176.789338]  block group used 0
[43176.789341]  item 43 key (1013878161408 192 3221225472) itemoff 2399 
itemsize 24

[43176.789342]  block group used 0
[43176.789345]  item 44 key (1017099386880 192 3221225472) itemoff 2375 
itemsize 24

[43176.789346]  block group used 0
[43176.789350]  item 45 key (1020320612352 192 3221225472) itemoff 2351 
itemsize 24

[43176.789351]  block group used 0
[43176.789354]  item 46 key (1023541837824 192 3221225472) itemoff 2327 
itemsize 24

[43176.789355]  block group used 0
[43176.789358]  item 47 key (1026763063296 192 3221225472) itemoff 2303 
itemsize 24

[43176.789360]  block group used 0
[43176.789363]  item 48 key (1029984288768 192 3221225472) itemoff 2279 
itemsize 24

[43176.789364]  block group used 0
[43176.789367]  item 49 key (1033205514240 192 3221225472) itemoff 2255 
itemsize 24

[43176.789368]  block group used 0
[43176.789371]  item 50 key (1036426739712 192 3221225472) itemoff 2231 
itemsize 24

[43176.789373]  block group used 0
[43176.789376]  item 51 key (1039647965184 192 3221225472) itemoff 2207 
itemsize 24

[43176.789377]  block group used 0
[43176.789380]  item 52 key (1042869190656 192 3221225472) itemoff 2183 
itemsize 24

[43176.789381]  block group used 0
[43176.789385]  item 53 key (1046090416128 192 3221225472) itemoff 2159 
itemsize 24

[43176.789386]  block group used 0
[43176.789389]  item 54 key (1049311641600 192 3221225472) itemoff 2135 
itemsize 24

[43176.789390]  block group used 0
[43176.789393]  item 55 key (1052532867072 192 3221225472) itemoff 2111 
itemsize 24

[43176.789395]  block group used 0
[43176.789399] BTRFS error (device sde): unable to find ref byte nr 
952574226432 parent 0 root 3  owner 0 offset 0
[43176.789409] BTRFS: error (device sde) in __btrfs_free_extent:6953: 
errno=-2 No such entry
[43176.789418] BTRFS: error (device sde) in btrfs_run_delayed_refs:2960: 
errno=-2 No such entry

[43176.823989] pending csums is 4096

Am 09.09.2016 um 22:21 schrieb Liu Bo:

On Fri, Sep 09, 2016 at 02:41:45PM +0200, Jan Koester wrote:




Hi,

i got from btrfs scrub command segfault. I use btrfs tools 4.7.2.

root@dibsi:/home/jan# btrfs scrub status /local
Speicherzugriffsfehler
root@dibsi:/home/jan# dmesg
[78294.556713] BTRFS error (device sda): bad tree block start 
18427384836265136347 2304683610112
[78294.556956] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558323] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558397] [ cut here ]
[78294.569900] kernel BUG at fs/btrfs/ctree.c:5202!
[78294.581634] invalid opcode:  [#15] SMP
[78294.593089] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs 
libcrc32c binfmt_misc btrfs xor raid6_pq kvm_amd kvm irqbypass serio_raw 
snd_usb_audio input_leds joydev snd_usbmidi_lib snd_hda_codec_hdmi edac_mce_amd 
snd_hda_intel edac_core snd_hda_codec k10temp snd_ctxfi snd_hda_core snd_hwdep 
snd_pcm i2c_piix4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq 
snd_seq_device snd_timer snd soundcore tpm_infineon mac_hid 8250_fintek shpchp 
sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid amdkfd 
amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea 
sysfillrect sysimgblt ptp fb_sys_fops r8169 drm mii ahci pps_core libahci wmi 
fjes
[78294.629504] CPU: 3 PID: 16486 Comm: btrfs Tainted: G  D W   
4.6.0-rc4 #1
[78294.629506] Hardware name: Gigabyte Technology Co., Ltd. 
GA-970A-D3/GA-970A-D3, BIOS F12 09/03/2013
[78294.629510] task: 880070766800 ti: 8801c2d3 task.ti: 
8801c2d3
[78294.629568] RIP: 0010:[]  [] 
btrfs_search_forward+0x24d/0x330 [btrfs]
[78294.629572] RSP: 0018:8801c2d33c10  EFLAGS: 00010246
[78294.629581] RAX:  RBX:  RCX: 0001
[78294.629583] RDX: 0001 RSI:  RDI: 880080638d40
[78294.629585] RBP: 8801c2d33c70 R08: 021899d9 R09: 02189fd9
[78294.629587] R10:  R11: 0003 R12: 88008826e8c0

Re: segfault btrfs scrub

2016-09-10 Thread Jan Koester

[43176.789311]  block group used 0
[43176.789314]  item 37 key (994550808576 192 3221225472) itemoff 2543 
itemsize 24

[43176.789315]  block group used 0
[43176.789319]  item 38 key (997772034048 192 3221225472) itemoff 2519 
itemsize 24

[43176.789320]  block group used 0
[43176.789323]  item 39 key (1000993259520 192 3221225472) itemoff 2495 
itemsize 24

[43176.789324]  block group used 0
[43176.789327]  item 40 key (1004214484992 192 3221225472) itemoff 2471 
itemsize 24

[43176.789329]  block group used 0
[43176.789332]  item 41 key (1007435710464 192 3221225472) itemoff 2447 
itemsize 24

[43176.789333]  block group used 0
[43176.789336]  item 42 key (1010656935936 192 3221225472) itemoff 2423 
itemsize 24

[43176.789338]  block group used 0
[43176.789341]  item 43 key (1013878161408 192 3221225472) itemoff 2399 
itemsize 24

[43176.789342]  block group used 0
[43176.789345]  item 44 key (1017099386880 192 3221225472) itemoff 2375 
itemsize 24

[43176.789346]  block group used 0
[43176.789350]  item 45 key (1020320612352 192 3221225472) itemoff 2351 
itemsize 24

[43176.789351]  block group used 0
[43176.789354]  item 46 key (1023541837824 192 3221225472) itemoff 2327 
itemsize 24

[43176.789355]  block group used 0
[43176.789358]  item 47 key (1026763063296 192 3221225472) itemoff 2303 
itemsize 24

[43176.789360]  block group used 0
[43176.789363]  item 48 key (1029984288768 192 3221225472) itemoff 2279 
itemsize 24

[43176.789364]  block group used 0
[43176.789367]  item 49 key (1033205514240 192 3221225472) itemoff 2255 
itemsize 24

[43176.789368]  block group used 0
[43176.789371]  item 50 key (1036426739712 192 3221225472) itemoff 2231 
itemsize 24

[43176.789373]  block group used 0
[43176.789376]  item 51 key (1039647965184 192 3221225472) itemoff 2207 
itemsize 24

[43176.789377]  block group used 0
[43176.789380]  item 52 key (1042869190656 192 3221225472) itemoff 2183 
itemsize 24

[43176.789381]  block group used 0
[43176.789385]  item 53 key (1046090416128 192 3221225472) itemoff 2159 
itemsize 24

[43176.789386]  block group used 0
[43176.789389]  item 54 key (1049311641600 192 3221225472) itemoff 2135 
itemsize 24

[43176.789390]  block group used 0
[43176.789393]  item 55 key (1052532867072 192 3221225472) itemoff 2111 
itemsize 24

[43176.789395]  block group used 0
[43176.789399] BTRFS error (device sde): unable to find ref byte nr 
952574226432 parent 0 root 3  owner 0 offset 0
[43176.789409] BTRFS: error (device sde) in __btrfs_free_extent:6953: 
errno=-2 No such entry
[43176.789418] BTRFS: error (device sde) in btrfs_run_delayed_refs:2960: 
errno=-2 No such entry

[43176.823989] pending csums is 4096

Am 09.09.2016 um 22:21 schrieb Liu Bo:

On Fri, Sep 09, 2016 at 02:41:45PM +0200, Jan Koester wrote:




Hi,

i got from btrfs scrub command segfault. I use btrfs tools 4.7.2.

root@dibsi:/home/jan# btrfs scrub status /local
Speicherzugriffsfehler
root@dibsi:/home/jan# dmesg
[78294.556713] BTRFS error (device sda): bad tree block start 
18427384836265136347 2304683610112
[78294.556956] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558323] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558397] [ cut here ]
[78294.569900] kernel BUG at fs/btrfs/ctree.c:5202!
[78294.581634] invalid opcode:  [#15] SMP
[78294.593089] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs 
libcrc32c binfmt_misc btrfs xor raid6_pq kvm_amd kvm irqbypass serio_raw 
snd_usb_audio input_leds joydev snd_usbmidi_lib snd_hda_codec_hdmi edac_mce_amd 
snd_hda_intel edac_core snd_hda_codec k10temp snd_ctxfi snd_hda_core snd_hwdep 
snd_pcm i2c_piix4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq 
snd_seq_device snd_timer snd soundcore tpm_infineon mac_hid 8250_fintek shpchp 
sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid amdkfd 
amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea 
sysfillrect sysimgblt ptp fb_sys_fops r8169 drm mii ahci pps_core libahci wmi 
fjes
[78294.629504] CPU: 3 PID: 16486 Comm: btrfs Tainted: G  D W   
4.6.0-rc4 #1
[78294.629506] Hardware name: Gigabyte Technology Co., Ltd. 
GA-970A-D3/GA-970A-D3, BIOS F12 09/03/2013
[78294.629510] task: 880070766800 ti: 8801c2d3 task.ti: 
8801c2d3
[78294.629568] RIP: 0010:[]  [] 
btrfs_search_forward+0x24d/0x330 [btrfs]
[78294.629572] RSP: 0018:8801c2d33c10  EFLAGS: 00010246
[78294.629581] RAX:  RBX:  RCX: 0001
[78294.629583] RDX: 0001 RSI:  RDI: 880080638d40
[78294.629585] RBP: 8801c2d33c70 R08: 021899d9 R09: 02189fd9
[78294.629587] R10:  R11: 0003 R12: 88008826e8c0

segfault btrfs scrub

2016-09-09 Thread Jan Koester

 
 
Hi,

i got from btrfs scrub command segfault. I use btrfs tools 4.7.2.
 
root@dibsi:/home/jan# btrfs scrub status /local
Speicherzugriffsfehler
root@dibsi:/home/jan# dmesg
[78294.556713] BTRFS error (device sda): bad tree block start 
18427384836265136347 2304683610112
[78294.556956] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558323] BTRFS error (device sda): bad tree block start 
17385487456874290426 2304683610112
[78294.558397] [ cut here ]
[78294.569900] kernel BUG at fs/btrfs/ctree.c:5202!
[78294.581634] invalid opcode:  [#15] SMP
[78294.593089] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs 
libcrc32c binfmt_misc btrfs xor raid6_pq kvm_amd kvm irqbypass serio_raw 
snd_usb_audio input_leds joydev snd_usbmidi_lib snd_hda_codec_hdmi edac_mce_amd 
snd_hda_intel edac_core snd_hda_codec k10temp snd_ctxfi snd_hda_core snd_hwdep 
snd_pcm i2c_piix4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq 
snd_seq_device snd_timer snd soundcore tpm_infineon mac_hid 8250_fintek shpchp 
sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid amdkfd 
amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper e1000e syscopyarea 
sysfillrect sysimgblt ptp fb_sys_fops r8169 drm mii ahci pps_core libahci wmi 
fjes
[78294.629504] CPU: 3 PID: 16486 Comm: btrfs Tainted: G  D W   
4.6.0-rc4 #1
[78294.629506] Hardware name: Gigabyte Technology Co., Ltd. 
GA-970A-D3/GA-970A-D3, BIOS F12 09/03/2013
[78294.629510] task: 880070766800 ti: 8801c2d3 task.ti: 
8801c2d3
[78294.629568] RIP: 0010:[]  [] 
btrfs_search_forward+0x24d/0x330 [btrfs]
[78294.629572] RSP: 0018:8801c2d33c10  EFLAGS: 00010246
[78294.629581] RAX:  RBX:  RCX: 0001
[78294.629583] RDX: 0001 RSI:  RDI: 880080638d40
[78294.629585] RBP: 8801c2d33c70 R08: 021899d9 R09: 02189fd9
[78294.629587] R10:  R11: 0003 R12: 88008826e8c0
[78294.629589] R13: 0001 R14: 0001 R15: 
[78294.629593] FS:  7ff69486f8c0() GS:88022fcc() 
knlGS:e71e3b40
[78294.629595] CS:  0010 DS:  ES:  CR0: 80050033
[78294.629598] CR2: 01a94088 CR3: 000221fe6000 CR4: 06e0
[78294.629599] Stack:
[78294.629605]  024280ca 8801c2d33cbf 880223bfa800 
01ff
[78294.629609]  d800 0001 db9fb905 
88008826e8c0
[78294.629613]  8801c2d33d18 8802008ee000 8801c2d33cbf 
8801f91e6800
[78294.629614] Call Trace:
[78294.629669]  [] search_ioctl+0xf2/0x1a0 [btrfs]
[78294.629720]  [] btrfs_ioctl_tree_search+0x72/0xc0 [btrfs]
[78294.629769]  [] btrfs_ioctl+0x3e4/0x21a0 [btrfs]
[78294.629777]  [] ? handle_mm_fault+0x14cf/0x1e60
[78294.629782]  [] ? cp_new_stat+0x153/0x180
[78294.629789]  [] do_vfs_ioctl+0xa1/0x5b0
[78294.629794]  [] ? __do_page_fault+0x205/0x4d0
[78294.629800]  [] SyS_ioctl+0x79/0x90
[78294.629806]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
[78294.629847] Code: 8b 4d a0 48 8b 55 a8 4d 89 f8 48 8b 7d b0 4c 89 e6 e8 68 
fb ff ff 85 c0 0f 85 bf 00 00 00 4c 89 e7 e8 88 7f ff ff e9 fa fd ff ff <0f> 0b 
48 8d 04 92 43 89 54 ac 40 48 8d 75 bf b9 11 00 00 00 48
[78294.629885] RIP  [] btrfs_search_forward+0x24d/0x330 
[btrfs]
[78294.629887]  RSP 
[78294.629969] ---[ end trace fa1ffcf4f496deaf ]---
--
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


cannot repair raid6 volume rescue zero-log crashed

2016-02-27 Thread Jan Koester
Hi,
 
cannot recover my home filesystem.
 
Linux dibsi 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
 
btrfs --version
btrfs-progs v4.4

btrfs fi show
Label: 'root'  uuid: 3d279e92-d021-4a57-92b8-db3bfcbba79d
Total devices 1 FS bytes used 74.47GiB
devid1 size 111.79GiB used 82.02GiB path /dev/sdf1

Label: none  uuid: 73d4dc77-6ff3-412f-9b0a-0d11458faf32
Total devices 5 FS bytes used 1.17TiB
devid1 size 931.51GiB used 420.78GiB path /dev/sdb
devid2 size 931.51GiB used 420.78GiB path /dev/sdc
devid3 size 931.51GiB used 420.78GiB path /dev/sdd
devid4 size 931.51GiB used 420.78GiB path /dev/sde
devid5 size 931.51GiB used 420.78GiB path /dev/sda

 
btrfs rescue zero-log:

root@dibsi:/home/jan# gdb --args btrfs rescue zero-log 
/dev/disk/by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from btrfs...done.
(gdb) r
Starting program: /usr/local/bin/btrfs rescue zero-log 
/dev/disk/by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
parent transid verify failed on 2280450637824 wanted 861168 found 860380
parent transid verify failed on 2280450637824 wanted 861168 found 860380
checksum verify failed on 2280450637824 found BF5F5D16 wanted AE725F92
checksum verify failed on 2280450637824 found BF5F5D16 wanted AE725F92
bytenr mismatch, want=2280450637824, have=15938376490240
Clearing log on /dev/disk/by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32, 
previous log_root 2280534142976, level 0
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted 

cannot repair filesystem

2016-01-01 Thread Jan Koester
Hi,

if I try to repair filesystem got I'am assert. I use Raid6.

Linux dibsi 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt4-3~bpo70+1 
(2015-02-12) x86_64 GNU/Linux

root@dibsi:~/btrfs-progs# btrfs fi show
Label: none  uuid: 6a2f3936-d0ef-43c0-9815-41e24f2bc21a
Total devices 1 FS bytes used 26.63GiB
devid1 size 111.70GiB used 49.04GiB path /dev/sdf2

Label: none  uuid: 73d4dc77-6ff3-412f-9b0a-0d11458faf32
Total devices 5 FS bytes used 1.17TiB
devid1 size 931.51GiB used 420.78GiB path /dev/sdb
devid2 size 931.51GiB used 420.78GiB path /dev/sdc
devid3 size 931.51GiB used 420.78GiB path /dev/sdd
devid4 size 931.51GiB used 420.78GiB path /dev/sde
devid5 size 931.51GiB used 420.78GiB path /dev/sda

root@dibsi:~/btrfs-progs# btrfs check --repair 
/dev/disk/by-uuid/73d4dc77-6ff3-412f-9b0a-0d11458faf32 
enabling repair mode
parent transid verify failed on 2280450637824 wanted 861168 found 860380
parent transid verify failed on 2280450637824 wanted 861168 found 860380
checksum verify failed on 2280450637824 found BF5F5D16 wanted AE725F92
checksum verify failed on 2280450637824 found BF5F5D16 wanted AE725F92
bytenr mismatch, want=2280450637824, have=15938376490240
repair mode will force to clear out log tree, Are you sure? [y/N]: y
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223
bytenr mismatch, want=2280260939776, have=15937230354176
parent transid verify failed on 2280260939776 wanted 861166 found 860368
parent transid verify failed on 2280260939776 wanted 861166 found 860368
checksum verify failed on 2280260939776 found 816E966C wanted CB60A223