On Thu, Jan 03, 2013 at 05:26:38AM -0700, Richard Cooper wrote: > Hi All, > > I'm trying to repair a broken fs using btrfsck and am hitting a failed > assertion. I'd appreciate any suggestions for what to do next. Is there any > thing I can do to help fix this bug? Any other information from my FS which > would help? If the FS could be salvaged that would be a bonus, but I'm more > interested in providing a useful bug report before wiping the disk. >
Well good news is that its the allocator failing to find space for a new block, and the allocator in btrfs-progs is under-tested, so it's likely just an internal bug and something we can fix. Can you do btrfs fi show /dev/md4 (not mounted) and post that so we can be sure there's actually enough space. And I'll look at the allocator code in the meantime and see if theres something obvious wrong. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
