From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>,
Thorsten Hirsch <t.hirsch@web.de>,
linux-btrfs@vger.kernel.org
Subject: Re: tree first key mismatch detected (reproducible error)
Date: Sat, 25 Jan 2020 20:23:45 +0800 [thread overview]
Message-ID: <71251506-88e5-c481-abdf-56dcd625b139@gmx.com> (raw)
In-Reply-To: <688e0961-c80e-4db0-bf87-dabbfc72adf1@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 5266 bytes --]
On 2020/1/25 下午7:46, Andrei Borzenkov wrote:
> 25.01.2020 14:37, Thorsten Hirsch пишет:
>> Hi, here's a btrfs problem that started happening today on my main computer:
>>
>> BTRFS error (device nvme0n1p3): tree first key mismatch detected,
>> bytenr=109690880 parent_transid=1329869 key
>> expected=(48044838912,168,12288) has=(48045363200,168,12288)
>>
>
> This looks like bit flip
>
> 48044838912 == B2FB21000
> 48045363200 == B2FBA1000
>
> with usual recommendation to check your RAM.
>
Ops, forgot the case of bitflip.
Just as mentioned by Andrei, make sure the memory problem is solved,
then `btrfs check`.
Thanks,
Qu
>> It always occurs some minutes after booting, sometimes even seconds
>> after booting. The partition is then remounted read-only. I already
>> tried scrubbing the partition (aborts itself after some seconds) and
>> balancing (seems to trigger the error immediately and doesn't even
>> start).
>>
>> I attached some more output of dmesg. The distribution is Arch Linux
>> and the kernel is the most recent one in Arch's default kernel
>> package: 5.4.14-arch1-1 (I upgraded from 5.4.13 to 5.4.14 just
>> yesterday).
>>
>> Best regards,
>> Thorsten
>>
>> [Jan25 12:00] BTRFS error (device nvme0n1p3): tree first key mismatch
>> detected, bytenr=109690880 parent_transid=1329869 key
>> expected=(48044838912,168,12288) has=(48045363200,168,12288)
>> [ +0,000003] ------------[ cut here ]------------
>> [ +0,000001] BTRFS: Transaction aborted (error -117)
>> [ +0,000041] WARNING: CPU: 7 PID: 382 at fs/btrfs/extent-tree.c:3080
>> __btrfs_free_extent.isra.0+0x694/0x9e0 [btrfs]
>> [ +0,000000] Modules linked in: xt_nat xt_tcpudp veth xt_conntrack
>> xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo
>> xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
>> nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc edac_mce_amd
>> kvm_amd snd_hda_codec_ca0110 snd_hda_codec_generic wmi_bmof kvm
>> ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt pktcdvd
>> irqbypass snd_hda_codec uvcvideo snd_hda_core snd_hwdep
>> videobuf2_vmalloc snd_pcm videobuf2_memops nls_iso8859_1
>> videobuf2_v4l2 nls_cp437 videobuf2_common snd_timer crct10dif_pclmul
>> vfat crc32_pclmul videodev fat snd joydev ghash_clmulni_intel
>> input_leds mousedev mc psmouse aesni_intel r8169 crypto_simd realtek
>> cryptd ccp glue_helper k10temp i2c_piix4 soundcore libphy rng_core wmi
>> gpio_amdpt evdev mac_hid pinctrl_amd acpi_cpufreq fuse vboxnetflt(OE)
>> vboxnetadp(OE) vboxdrv(OE) sg crypto_user ip_tables x_tables sr_mod
>> cdrom sd_mod hid_generic usbhid hid serio_raw atkbd libps2 ahci
>> libahci libata xhci_pci
>> [ +0,000018] xhci_hcd scsi_mod i8042 serio amdgpu gpu_sched
>> i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt
>> fb_sys_fops drm agpgart btrfs libcrc32c crc32c_generic crc32c_intel
>> xor raid6_pq
>> [ +0,000005] CPU: 7 PID: 382 Comm: btrfs-transacti Tainted: G
>> OE 5.4.14-arch1-1 #1
>> [ +0,000001] Hardware name: Gigabyte Technology Co., Ltd.
>> AB350M-DS3H/AB350M-DS3H-CF, BIOS F50a 11/27/2019
>> [ +0,000010] RIP: 0010:__btrfs_free_extent.isra.0+0x694/0x9e0 [btrfs]
>> [ +0,000001] Code: e8 c1 ee 00 00 8b 4c 24 38 85 c9 0f 84 39 fe ff ff
>> 48 8b 54 24 48 e9 04 fe ff ff 44 89 fe 48 c7 c7 a0 ce 30 c0 e8 ba 48
>> c4 d1 <0f> 0b 48 8b 3c 24 44 89 f9 ba 08 0c 00 00 48 c7 c6 a0 20 30 c0
>> e8
>> [ +0,000001] RSP: 0018:ffff8fc081363ba0 EFLAGS: 00010286
>> [ +0,000001] RAX: 0000000000000000 RBX: 0000000000000192 RCX: 0000000000000000
>> [ +0,000000] RDX: 0000000000000001 RSI: 0000000000000096 RDI: 00000000ffffffff
>> [ +0,000001] RBP: 0000000b3090a000 R08: 000000000000049b R09: 0000000000000004
>> [ +0,000000] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8b958a1c9c40
>> [ +0,000001] R13: 0000000000000000 R14: 0000000000000001 R15: 00000000ffffff8b
>> [ +0,000001] FS: 0000000000000000(0000) GS:ffff8b958e9c0000(0000)
>> knlGS:0000000000000000
>> [ +0,000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> [ +0,000001] CR2: 00007fdcf263d000 CR3: 000000032f11a000 CR4: 00000000003406e0
>> [ +0,000001] Call Trace:
>> [ +0,000012] ? __btrfs_run_delayed_refs+0xc9f/0xff0 [btrfs]
>> [ +0,000009] __btrfs_run_delayed_refs+0x25e/0xff0 [btrfs]
>> [ +0,000011] btrfs_run_delayed_refs+0x6a/0x180 [btrfs]
>> [ +0,000013] btrfs_start_dirty_block_groups+0x28e/0x470 [btrfs]
>> [ +0,000011] btrfs_commit_transaction+0x116/0x9b0 [btrfs]
>> [ +0,000003] ? _raw_spin_unlock+0x16/0x30
>> [ +0,000010] ? join_transaction+0x108/0x3a0 [btrfs]
>> [ +0,000010] transaction_kthread+0x13a/0x180 [btrfs]
>> [ +0,000002] kthread+0xfb/0x130
>> [ +0,000010] ? btrfs_cleanup_transaction+0x560/0x560 [btrfs]
>> [ +0,000001] ? kthread_park+0x90/0x90
>> [ +0,000001] ret_from_fork+0x1f/0x40
>> [ +0,000002] ---[ end trace 51366456523028bd ]---
>> [ +0,000001] BTRFS: error (device nvme0n1p3) in
>> __btrfs_free_extent:3080: errno=-117 unknown
>> [ +0,000001] BTRFS info (device nvme0n1p3): forced readonly
>> [ +0,000002] BTRFS: error (device nvme0n1p3) in
>> btrfs_run_delayed_refs:2188: errno=-117 unknown
>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-25 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 11:37 tree first key mismatch detected (reproducible error) Thorsten Hirsch
2020-01-25 11:46 ` Andrei Borzenkov
2020-01-25 12:23 ` Qu Wenruo [this message]
2020-01-25 15:44 ` Thorsten Hirsch
2020-01-25 16:01 ` Martin Raiber
2020-01-26 11:17 ` Thorsten Hirsch
2020-01-26 13:03 ` Qu Wenruo
2020-01-25 12:15 ` Qu Wenruo
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=71251506-88e5-c481-abdf-56dcd625b139@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=t.hirsch@web.de \
/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