All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lewis Diamond <me@lewisdiamond.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs check --readonly crash
Date: Sat, 30 Jun 2018 21:59:14 -0400	[thread overview]
Message-ID: <CAHwd=GkFPxS=nOviDs41+e-JNXX1QWLctP=hb-rO=vCJiyuFDA@mail.gmail.com> (raw)

Hi,
I've been told to report this issue to this mailing list.

sudo btrfs check --readonly /dev/sdc
Checking filesystem on /dev/sdc
UUID: 2630aec8-8399-4bd8-9397-8c04953a35d5
checking extents
checking free space cache
there is no free space entry for 1596152365056-1596152381440
there is no free space entry for 1596152365056-1597220323328
cache appears valid but isn't 1596146581504
there is no free space entry for 1613348585472-1613348618240
there is no free space entry for 1613348585472-1614400192512
cache appears valid but isn't 1613326450688
block group 1645538705408 has wrong amount of free space, free space
cache has 58212352 block group has 58277888
failed to load free space cache for block group 1645538705408
block group 1683119669248 has wrong amount of free space, free space
cache has 52838400 block group has 52953088
failed to load free space cache for block group 1683119669248
btrfs: unable to add free space :-17
free-space-cache.c:843: btrfs_add_free_space: BUG_ON `ret == -EEXIST`
triggered, value 1
btrfs(+0x37337)[0x556024d5d337]
btrfs(btrfs_add_free_space+0x11d)[0x556024d5da2d]
btrfs(load_free_space_cache+0xde9)[0x556024d5e889]
btrfs(cmd_check+0x15fe)[0x556024d8b9ee]
btrfs(main+0x88)[0x556024d38768]
/usr/lib/libc.so.6(__libc_start_main+0xeb)[0x7f9382a9506b]
btrfs(_start+0x2a)[0x556024d3888a]
Aborted


This happened on a USB HDD duo in raid 1 which had btrfs issues
(probably due to a bad controller). One of the hdd was subsequently
dropped by a 2 year old (causing subsequent checks to crash).

-Lewis

             reply	other threads:[~2018-07-01  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01  1:59 Lewis Diamond [this message]
2018-07-01  2:07 ` btrfs check --readonly crash Qu Wenruo
2018-07-01 18:01   ` Lewis Diamond
2018-07-01 19:00     ` Chris Murphy
2018-07-02  0:03     ` 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='CAHwd=GkFPxS=nOviDs41+e-JNXX1QWLctP=hb-rO=vCJiyuFDA@mail.gmail.com' \
    --to=me@lewisdiamond.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.