Your message dated Sun, 16 Jun 2019 14:42:26 +0200 with message-id <[email protected]> and subject line almost certainly fixed has caused the Debian Bug report #703474, regarding /sbin/btrfsck: btrfsck does an infinite loop with --repair on i386 not on amd64 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 703474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703474 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: btrfs-tools Version: 0.19+20130131-3+really20121004-1 Severity: important File: /sbin/btrfsck Tags: upstream Below is the gdb backtrace from a version of btrfs-tools that I built with debugging support. Both the debugging version I compiled and the versions in the Debian repository (both the "wheezy" 0.19+20120328-7.1 and "unstable" 0.19+20130131-3+really20121004-1 versions) hang after a few minutes. When it hangs it makes no system calls and is just in a CPU loop. The same filesystem image when checked on AMD64 will complete. This is an issue for me at the moment because the bootable USB device I use for recovering unbootable systems is i386. But it will also affect anyone who uses BTRFS on i386. Program received signal SIGINT, Interrupt. 0x08074c03 in rb_next (node=0x8149498) at rbtree.c:338 338 rbtree.c: No such file or directory. (gdb) bt #0 0x08074c03 in rb_next (node=0x8149498) at rbtree.c:338 #1 0x08074f25 in __tree_search (root=0x809f18c, offset=47318015451136, size=1, prev_ret=0xbffff230) at extent-cache.c:77 #2 0x08075142 in find_first_cache_extent (tree=0x809f18c, start=47318015451136) at extent-cache.c:138 #3 0x0807603c in find_first_extent_bit (tree=0x809f18c, start=47318015451136, start_ret=0xbffff2e0, end_ret=0xbffff2e8, bits=22) at extent_io.c:438 #4 0x0806339e in btrfs_lookup_block_group (info=0x809f108, bytenr=47318015451136) at extent-tree.c:213 #5 0x080678cf in update_pinned_extents (root=0x809d240, bytenr=47318015451136, num=1013489549123370216, pin=1) at extent-tree.c:1895 #6 0x080680b7 in btrfs_pin_extent (fs_info=0x809f108, bytenr=210453397504, num_bytes=1013536656685423848) at extent-tree.c:2062 #7 0x08053eed in check_extent_refs (trans=0x809dbf0, root=0x81780b0, extent_cache=0xbffff474, repair=1) at btrfsck.c:3294 #8 0x080547bf in check_extents (trans=0x809dbf0, root=0x81780b0, repair=1) at btrfsck.c:3461 #9 0x08054c7e in main (ac=1, av=0xbffff814) at btrfsck.c:3585 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages btrfs-tools depends on: ii e2fslibs 1.42.5-1 ii libc6 2.13-38 ii libcomerr2 1.42.5-1 ii libuuid1 2.20.1-5.3 ii zlib1g 1:1.2.7.dfsg-13 btrfs-tools recommends no packages. btrfs-tools suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---> Found in version btrfs-tools/0.19+20130131-3+really20121004-1 This version is so old, from the very beginning of btrfs being in mainline, that it'd be a waste of time to even try to reproduce the bug (and you pretty surely don't have the filesystem in question anymore). The code in question underwent lots of changes including near-complete refactorings, thus the bug is pretty certainly gone (and replaced by fresh ones). Thus, closing. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ A true bird-watcher waves his tail while doing so. ⠈⠳⣄⠀⠀⠀⠀
--- End Message ---
