All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Munteanu <robert.munteanu@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: btrfs partition fails to mount - kernel BUG at ../fs/btrfs/extent-tree.c:1872
Date: Thu, 25 Aug 2016 01:19:27 +0300	[thread overview]
Message-ID: <CAC8ULPbST1tMtfW8MBdEXiFSxknQtUHYneZu8FpQij5DRon_gg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]

Hi,

Using Kernel 4.7.1 ( openSUSE Tumbleweed x86_64 ), btrfsprogs 4.7 I
always get a hard lockup when trying to mount my btrfs root partition.

This may be due to some previous errors which only manifested
themselves now, as it's been converted from an ext4 partition.

Using mount -o ro works. Using mount -o recovery or mounting without
arguments does not. I've managed to capture one of the error messages,
but via screenshot only. I've transcribed some of it below, more at

  http://i.imgur.com/OSIddHE.jpg

BTRFS info (device sda1): disk space caching is enabled
BTRFS info (device sda1): detected SSD devices, enabling SSD mode
BTRFS info (device sda1): checking UUID tree
BTRFS info (device sda1): continuing balance
BTRFS info (device sda1): relocating block group 1047892328448 flags 1
BTRFS info (device sda1): found 805 extents
(...)
kernel BUG at ../fs/btrfs/extent-tree.c:1872
invalid opcode: 0000 [#1] PREEMPT SMP
(...)
Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs]
(...)
Call Trace:
 [...] remove_extent_backref
 [...] __btrfs_free_extent_isra
 [...] __btrfs_run_delayed
 [...] delayed_ref_async_start
 [...] btrfs_scrubparity_helper
 [...] process_one_work
 [...] worked_thread
 [...] kthread
 [...] ret_from_fork
DWARF2 unwinder stuck at ret_from_fork

For reference, I've attached the output of

- btrfsck /dev/sda1
- btrfsck --repair /dev/sda1
- btrfsck --repair /dev/sda1 (2nd execution)

I've included two executions in repair mode to show that nothing of
interest changes between the two.

My way out is simply transferring the data out ( mount -o ro works )
and creating a new partition, but it would be interesting to fix it,
and if there's any information I can offer to help prepare a bug fix
please let me know.

Thanks,

Robert

-- 
http://robert.muntea.nu/

[-- Attachment #2: btrfsck.out --]
[-- Type: application/octet-stream, Size: 341 bytes --]

Checking filesystem on /dev/sda1
UUID: 54dea125-74cd-4bb2-86a2-f7bc645b76cf
found 194953592845 bytes used err is 0
total csum bytes: 185735760
total tree bytes: 4298801152
total fs tree bytes: 3928309760
total extent tree bytes: 144261120
btree space waste bytes: 801786863
file data blocks allocated: 1455292370944
 referenced 324826996736

[-- Attachment #3: btrfsck_repair.out --]
[-- Type: application/octet-stream, Size: 434 bytes --]

enabling repair mode
Checking filesystem on /dev/sda1
UUID: 54dea125-74cd-4bb2-86a2-f7bc645b76cf
cache and super generation don't match, space cache will be invalidated
found 194953576461 bytes used err is 0
total csum bytes: 185735760
total tree bytes: 4298784768
total fs tree bytes: 3928309760
total extent tree bytes: 144244736
btree space waste bytes: 801769889
file data blocks allocated: 1455292370944
 referenced 324826996736

[-- Attachment #4: btrfsck_repair_2.out --]
[-- Type: application/octet-stream, Size: 434 bytes --]

enabling repair mode
Checking filesystem on /dev/sda1
UUID: 54dea125-74cd-4bb2-86a2-f7bc645b76cf
cache and super generation don't match, space cache will be invalidated
found 194956742669 bytes used err is 0
total csum bytes: 185735760
total tree bytes: 4298784768
total fs tree bytes: 3928309760
total extent tree bytes: 144244736
btree space waste bytes: 801769740
file data blocks allocated: 1455292370944
 referenced 324826996736

             reply	other threads:[~2016-08-24 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 22:19 Robert Munteanu [this message]
2016-08-25  2:32 ` btrfs partition fails to mount - kernel BUG at ../fs/btrfs/extent-tree.c:1872 Duncan
2016-08-25  6:29 ` Robert Munteanu
2016-08-25 20:06 ` Robert Munteanu
2016-10-19 17:24   ` Dāvis Mosāns

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=CAC8ULPbST1tMtfW8MBdEXiFSxknQtUHYneZu8FpQij5DRon_gg@mail.gmail.com \
    --to=robert.munteanu@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.