On Wed, Jul 6, 2016 at 3:55 AM, Stanislaw Kaminski <stasheck.fora@xxxxxxxxx> wrote: > Device unallocated: 97.89GiB There should be no problem creating any type of block group from this much space. It's a bug. I would try regression testing. Kernel 4.5.7 has some changes that may or may not relate to this (they should only relate when there is no unallocated space left) so you could try 4.5.6 and 4.5.7. And also 4.4.14. But also the kernel messages are important. There is this obscure enospc with error -28, so either with or without enospc_debug mount option is useful to try in 4.6.3 (I think it's less useful in older kernels). But do try nospace_cache first. If that works, you could then mount with clear_cache one time and see if that provides an enduring fix. It can take some time to rebuild the cache after clear_cache is used. -- Chris Murphy -- 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
