From: Karl-Philipp Richter <richter@richtercloud.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: "btrfs_reserve_extent: Assertion `ret` failed." during btrfsck --init-csum-tree
Date: Mon, 05 Jan 2015 12:38:15 +0100 [thread overview]
Message-ID: <54AA77A7.50509@richtercloud.de> (raw)
In-Reply-To: <549210D9.4060302@richtercloud.de>
This is fixed in btrfs-progs 3.18 (tested on Linux 3.17.7).
Am 18.12.2014 um 00:25 schrieb Karl-Philipp Richter:
> Hi together,
> after a btrfs was missing some csums and therefore remounted read-only,
> I unmounted it and experienced
>
> $ sudo btrfsck --init-csum-tree /dev/sde1
> Creating a new CRC tree
> Checking filesystem on /dev/sde1
> UUID: bd6298ea-0748-45fe-87c8-eace6793ca89
> Reinit crc root
> extent-tree.c:2657: btrfs_reserve_extent: Assertion `ret` failed.
> btrfs check[0x43d6c1]
> btrfs check(btrfs_reserve_extent+0xb63)[0x443111]
> btrfs check(btrfs_alloc_free_block+0x5a)[0x44318c]
> btrfs check[0x436585]
> btrfs check(btrfs_search_slot+0x11d1)[0x4382fc]
> btrfs check(btrfs_csum_file_block+0x3ce)[0x4477cc]
> btrfs check(cmd_check+0xef2)[0x425ef5]
> btrfs check(main+0x15d)[0x40991d]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f405dcf8ec5]
> btrfs check[0x4094d9]
>
> with btrfs-progs 3.18-rc1 on Linux 3.17.6. What could that mean?
>
> -Kalle
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-01-05 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 23:25 "btrfs_reserve_extent: Assertion `ret` failed." during btrfsck --init-csum-tree Karl-Philipp Richter
2015-01-05 11:38 ` Karl-Philipp Richter [this message]
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=54AA77A7.50509@richtercloud.de \
--to=richter@richtercloud.de \
--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.