Version-Release number of selected component: btrfs-progs-4.14.1-1.fc28 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: btrfs check --repair /dev/sda5 crash_function: btrfs_set_key_blockptr executable: /usr/sbin/btrfs journald_cursor: s=66d65907be5742629cfe6892c4f30354;i=3bec;b=b7640cfb6d23450eb04a1d76b82ae9a2;m=7d15bce4;t=56398fabea79d;x=84c39af6d281b15f kernel: 4.15.0-0.rc9.git0.1.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 btrfs_set_key_blockptr at ctree.h:1758 #1 btrfs_set_node_blockptr at ctree.h:1775 #2 __btrfs_cow_block at ctree.c:314 #3 btrfs_cow_block at ctree.c:373 #4 btrfs_search_slot at ctree.c:1121 #5 btrfs_insert_empty_items at ctree.c:2485 #6 btrfs_insert_empty_item at ctree.h:2635 #7 btrfs_insert_item at ctree.c:2584 #8 btrfs_insert_inode at inode-item.c:155 #9 btrfs_make_root_dir at utils.c:397
Created attachment 1386053 [details] File: backtrace
Created attachment 1386054 [details] File: cgroup
Created attachment 1386055 [details] File: core_backtrace
Created attachment 1386056 [details] File: cpuinfo
Created attachment 1386057 [details] File: dso_list
Created attachment 1386058 [details] File: environ
Created attachment 1386059 [details] File: exploitable
Created attachment 1386060 [details] File: limits
Created attachment 1386061 [details] File: maps
Created attachment 1386062 [details] File: mountinfo
Created attachment 1386063 [details] File: open_fds
Created attachment 1386064 [details] File: proc_pid_status
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Similar problem has been detected: Maybe a forced shutdown corrupted my BTRFS partition, but now, nothing fixed it, even zero-logging the partition Whet I try 'btrfsck --repair /dev/sda5', it crashes [root@localhost mustafa]# btrfsck --repair /dev/sda5 enabling repair mode Checking filesystem on /dev/sda5 UUID: 24d374dc-9ebd-47b8-acda-c5a430e13d00 Fixed 0 roots. checking extents parent transid verify failed on 29360128 wanted 424 found 429 parent transid verify failed on 29360128 wanted 424 found 429 Ignoring transid failure leaf parent key incorrect 29360128 bad block 29360128 ERROR: errors found in extent allocation tree or chunk allocation checking free space cache cache and super generation don't match, space cache will be invalidated checking fs roots root 5 missing its root dir, recreating Failed to find [20971520, 168, 16384] btrfs unable to find ref byte nr 72531968 parent 0 root 5 owner 2 offset 0 parent transid verify failed on 29360128 wanted 424 found 429 Ignoring transid failure Segmentation fault (core dumped) reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: btrfsck --init-csum-tree /dev/sda5 crash_function: btrfs_set_key_blockptr executable: /usr/sbin/btrfs journald_cursor: s=4caec86794344cbaa278469d2c8480a1;i=dccde;b=1d91a9126f784f4581a991c1cb0182ac;m=7b49d94bb;t=572c4ee9cb763;x=faa69d7b816106e3 kernel: 4.17.11-200.fc28.x86_64 package: btrfs-progs-4.15.1-1.fc28 reason: btrfs killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
It would be best to report this to the upstream btrfs list if possible, I'm currently in much more of a packager mode than a maintainer mode for btrfs-progs at this point. You'll probably get more help and attention if you can post it to the list. Thanks, -Eric
(In reply to Eric Sandeen from comment #15) > It would be best to report this to the upstream btrfs list if possible, I'm > currently in much more of a packager mode than a maintainer mode for > btrfs-progs at this point. You'll probably get more help and attention if > you can post it to the list. > > Thanks, > -Eric Thanks, I added comments and logs with reference to this report here: https://github.com/kdave/btrfs-progs/issues/57
Thanks, of course if it gets resolved upstream, it will get pulled into Fedora when a btrfs-progs release contains the fix. Feel free to update this bug if things progress upstream, as well. Thanks, -Eric