On 11.07.2018 23:59, Pete wrote:
> On 07/10/2018 09:38 AM, Martin Raiber wrote:
>
>> This is probably a known issue. See
>> https://www.spinics.net/lists/linux-btrfs/msg75647.html
>> You could apply the patch in this thread and mount with enospc_debug to
>> confirm it is the same issue.
>> --
>> 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
>>
>
> OK, I've applied the patch, by hand, and hopefully put it in the right
> place. Need to learn to patch better.
>
> Booted the (rebuilt with make ; make modules_install syslinux etc)
> kernel with the option enospc_debug for the two btrfs file systems (1st
> entry for each in fstb. I was not expecting to get the issue to appear
> quickly as it took several days to hit previously. However, on checking
> I see another error, not sure if it is related, still is in extent-tree.c.
>
> https://drive.google.com/file/d/1K12MfpWFB1aHSXBga1Rym5terbmHeDfI/view?usp=sharing
This is just a warn_on saying that btrfs didn't manage to reserve space
for a CoW operation on the checksum tree ( so metadata). But did your
machine crash at that time, i.e why don't you paste the text but post
images?
>
>
> Pete
> --
> 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
>
--
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
