Re: Crashed filesystem, nothing helps
Now i do a btrfs-find-root, but it runs now since 5 day without a result. How long should i wait? Or is it already to late to hope? mainframe:~ # btrfs-find-root.static /dev/sdb1 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 Ignoring transid failure Superblock thinks the generation is 1490226 Superblock thinks the level is 1 The process is still running... Regards, Thomas -- Thomas Wurfbaum Starkertshofen 15 85084 Reichertshofen Tel.: +49-160-3696336 Mail: tho...@wurfbaum.net Google+:http://google.com/+ThomasWurfbaum Facebook: https://www.facebook.com/profile.php?id=16061335414 Xing: https://www.xing.com/profile/Thomas_Wurfbaum signature.asc Description: This is a digitally signed message part.
Re: Crashed filesystem, nothing helps
With the help of btrfs-corrupt-block i was able to get a little bit farer. I marked some of my problem block corrupt. Now i am in this stage mainframe:~ # btrfs restore /dev/sdb1 /mnt parent transid verify failed on 29409280 wanted 1486829 found 1488801 parent transid verify failed on 29409280 wanted 1486829 found 1488801 parent transid verify failed on 29409280 wanted 1486829 found 1488801 parent transid verify failed on 29409280 wanted 1486829 found 1488801 Ignoring transid failure parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 parent transid verify failed on 29376512 wanted 1327723 found 1489835 Ignoring transid failure parent transid verify failed on 29786112 wanted 1489835 found 1489871 parent transid verify failed on 29786112 wanted 1489835 found 1489871 parent transid verify failed on 29786112 wanted 1489835 found 1489871 parent transid verify failed on 29786112 wanted 1489835 found 1489871 Ignoring transid failure leaf parent key incorrect 29786112 Error searching -1 Regards, Thomas -- Thomas Wurfbaum Starkertshofen 15 85084 Reichertshofen Tel.: +49-160-3696336 Mail: tho...@wurfbaum.net Google+:http://google.com/+ThomasWurfbaum Facebook: https://www.facebook.com/profile.php?id=16061335414 Xing: https://www.xing.com/profile/Thomas_Wurfbaum signature.asc Description: This is a digitally signed message part.
Re: Crashed filesystem, nothing helps
Am Mittwoch, 2. August 2017, 11:31:41 CEST schrieb Roman Mamedov: > Did it just abruptly exit there? Or you terminated it? It apruptly stopped there Regards, Thomas -- Thomas Wurfbaum Starkertshofen 15 85084 Reichertshofen Tel.: +49-160-3696336 Mail: tho...@wurfbaum.net Google+:http://google.com/+ThomasWurfbaum Facebook: https://www.facebook.com/profile.php?id=16061335414 Xing: https://www.xing.com/profile/Thomas_Wurfbaum signature.asc Description: This is a digitally signed message part.
Re: Crashed filesystem, nothing helps
Maybe you are right, but i just followed the Suse guide: https://en.opensuse.org/SDB:BTRFS How to repair a broken/unmountable btrfs filesystem I already tried the commands mount with the -o usebackuproot option. (And -o usebackuproot,ro as well) But they just produce this in dmesg: [61054.470771] BTRFS info (device sdb1): trying to use backup root at mount time [61054.470778] BTRFS info (device sdb1): disk space caching is enabled [61054.470782] BTRFS info (device sdb1): has skinny extents [61054.560876] BTRFS error (device sdb1): parent transid verify failed on 29392896 wanted 1486833 found 1486836 [61054.563423] BTRFS error (device sdb1): parent transid verify failed on 29392896 wanted 1486833 found 1486836 [61054.604057] BTRFS error (device sdb1): open_ctree failed [61079.137435] BTRFS info (device sdb1): trying to use backup root at mount time [61079.137443] BTRFS info (device sdb1): disk space caching is enabled [61079.137445] BTRFS info (device sdb1): has skinny extents [61079.227242] BTRFS error (device sdb1): parent transid verify failed on 29392896 wanted 1486833 found 1486836 [61079.230087] BTRFS error (device sdb1): parent transid verify failed on 29392896 wanted 1486833 found 1486836 [61079.260062] BTRFS error (device sdb1): open_ctree failed And on the cli i get the following: mainframe:~ # mount -o usebackuproot,ro /dev/sdb1 /data mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. A restore does also not help: mainframe:~ # btrfs restore /dev/sdb1 /mnt parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 Ignoring transid failure parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 Ignoring transid failure parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 Ignoring transid failure -- Thomas Wurfbaum Starkertshofen 15 85084 Reichertshofen Tel.: +49-160-3696336 Mail: tho...@wurfbaum.net Google+:http://google.com/+ThomasWurfbaum Facebook: https://www.facebook.com/profile.php?id=16061335414 Xing: https://www.xing.com/profile/Thomas_Wurfbaum signature.asc Description: This is a digitally signed message part.
[no subject]
subscribe linux-btrfs -- 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: Crashed filesystem, nothing helps
Please find attached my dmesg.log Regards, Thomas[0.00] Linux version 4.11.8-2-default (geeko@buildhost) (gcc version 7.1.1 20170629 [gcc-7-branch revision 249772] (SUSE Linux) ) #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.11.8-2-default root=UUID=6b92e93a-86f2-4007-b374-4c7ad6a57063 resume=/dev/disk/by-id/scsi-1AMCC_J0827296748EC30067A8-part2 splash=silent quiet showopts [0.00] x86/fpu: x87 FPU will use FXSAVE [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbfea] usable [0.00] BIOS-e820: [mem 0xbfeb-0xbfee2fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbfee3000-0xbfee] ACPI data [0.00] BIOS-e820: [mem 0xbfef-0xbfef] reserved [0.00] BIOS-e820: [mem 0xf000-0xf3ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] DMI: System manufacturer System Product Name/M2N32 WS Professional, BIOS ASUS M2N32 WS Pro ACPI BIOS Revision 2001 05/05/2008 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x24 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C7FFF write-protect [0.00] C8000-F uncachable [0.00] MTRR variable ranges enabled: [0.00] 0 base 00 mask FF8000 write-back [0.00] 1 base 008000 mask FFC000 write-back [0.00] 2 base 00BFF0 mask F0 uncachable [0.00] 3 base 01 mask FF write-back [0.00] 4 base 02 mask FFC000 write-back [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] TOM2: 00024000 aka 9216M [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: update [mem 0xbff0-0x] usable ==> reserved [0.00] e820: last_pfn = 0xbfeb0 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f6040-0x000f604f] mapped at [8808000f6040] [0.00] Scanning 1 areas for low memory corruption [0.00] Base memory trampoline at [880800098000] 98000 size 24576 [0.00] BRK [0x1b3269000, 0x1b3269fff] PGTABLE [0.00] BRK [0x1b326a000, 0x1b326afff] PGTABLE [0.00] BRK [0x1b326b000, 0x1b326bfff] PGTABLE [0.00] BRK [0x1b326c000, 0x1b326cfff] PGTABLE [0.00] BRK [0x1b326d000, 0x1b326dfff] PGTABLE [0.00] BRK [0x1b326e000, 0x1b326efff] PGTABLE [0.00] BRK [0x1b326f000, 0x1b326] PGTABLE [0.00] BRK [0x1b327, 0x1b3270fff] PGTABLE [0.00] RAMDISK: [mem 0x36b91000-0x375b] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F7F20 24 (v02 Nvidia) [0.00] ACPI: XSDT 0xBFEE3100 54 (v01 Nvidia ASUSACPI 42302E31 AWRD ) [0.00] ACPI: FACP 0xBFEEB480 F4 (v03 Nvidia ASUSACPI 42302E31 AWRD ) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/8 (20170119/tbfadt-603) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/8 (20170119/tbfadt-603) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/PmTimerBlock: 32/8 (20170119/tbfadt-603) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/8 (20170119/tbfadt-603) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 128/8 (20170119/tbfadt-603) [0.00] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 8, using default 32 (20170119/tbfadt-708) [0.00] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 8, using default 16 (20170119/tbfadt-708) [0.00] ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 8, using default 32 (20170119/tbfadt-708) [0.00] ACPI: DSDT 0xBFEE3280 008189 (v01 NVIDIA AWRDACPI 1000 MSFT 0300) [0.00] ACPI: FACS 0xBFEB 40 [0.00] ACPI: FACS 0xBFEB 40 [0.00] ACPI: TCPA 0xBFEEB6C0 32 (v01 HTC
Crashed filesystem, nothing helps
Hello, Yesterday morning i recognized a hard reboot of my system, but the /data filesystem was not possible to mount. mainframe:~ # uname -a Linux mainframe 4.11.8-2-default #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) x86_64 x86_64 x86_64 GNU/Linux mainframe:~ # btrfs --version btrfs-progs v4.10.2+20170406 mainframe:~ # btrfs fi show Label: none uuid: 2276-0885-4683-ac04-477c27cfab80 Total devices 1 FS bytes used 2.88TiB devid1 size 4.53TiB used 2.92TiB path /dev/sdb1 mainframe:~ # btrfs restore /dev/sdb1 /mnt parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 Ignoring transid failure parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 Ignoring transid failure parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 Ignoring transid failure mainframe:~ # mount /dev/sdb1 /data mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mainframe:~ # mount -o usebackuproot /dev/sdb1 /data mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. mainframe:~ # btrfs check /dev/sdb1 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 parent transid verify failed on 29392896 wanted 1486833 found 1486836 Ignoring transid failure parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 parent transid verify failed on 29409280 wanted 1486829 found 1486833 Ignoring transid failure parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 parent transid verify failed on 29376512 wanted 1327723 found 1486833 Ignoring transid failure Checking filesystem on /dev/sdb1 UUID: 2276-0885-4683-ac04-477c27cfab80 checking extents parent transid verify failed on 290766848 wanted 1486826 found 1486085 parent transid verify failed on 290766848 wanted 1486826 found 1486085 parent transid verify failed on 290766848 wanted 1486826 found 1486085 parent transid verify failed on 290766848 wanted 1486826 found 1486085 Ignoring transid failure parent transid verify failed on 292339712 wanted 1486826 found 1486086 parent transid verify failed on 292339712 wanted 1486826 found 1486086 parent transid verify failed on 291078144 wanted 1486826 found 1486085 parent transid verify failed on 291078144 wanted 1486826 found 1486085 parent transid verify failed on 291078144 wanted 1486826 found 1486085 parent transid verify failed on 291078144 wanted 1486826 found 1486085 Ignoring transid failure parent transid verify failed on 292978688 wanted 1486826 found 1486086 parent transid verify failed on 292978688 wanted 1486826 found 1486086 parent transid verify failed on 292978688 wanted 1486826 found 1486086 parent transid verify failed on 292978688 wanted 1486826 found 1486086 Ignoring transid failure parent transid verify failed on 292519936 wanted 1486826 found 1486086 parent transid verify failed on 292519936 wanted 1486826 found 1486086 parent transid verify failed on 292536320 wanted 1486826 found 1486086 parent transid verify failed on 292536320 wanted 1486826 found 1486086 parent transid verify failed on 292552704 wanted 1486826 found 1486086 parent transid verify failed on 292552704 wanted 1486826 found 1486086 parent transid verify failed on 292585472 wanted 1486826 found 1486086 parent transid verify failed on 292585472 wanted 1486826 found 1486086 parent transid verify failed on 292585472 wanted 1486826 found 1486086 parent transid verify failed on 292585472 wanted 1486826 found 1486086 Ignoring transid failure parent transid verify failed on 290766848 wanted 1486826 found 1486085 Ignoring transid failure leaf parent key incorrect 290766848 bad block 290766848
