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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
