On 18.06.2021 19:36 Roman Mamedov wrote:

On Fri, 18 Jun 2021 16:18:40 +0000
Martin Raiber [off-list ref] wrote:

quoted

On 10.05.2021 00:14 Martin Raiber wrote:
the question is how can I trace where this error comes from... The error message points at btrfs_csum_file_blocks but nothing beyond that

Not entirely nothing, in theory the number afterwards is the line number of
source code (of btrfs/inode.c in this case) where the error occurred. But need
to check your specific patched sources, as if you patch Btrfs code the number
won't match with the mainline.

Yeah, the line points at this in inode.c:

    ret = add_pending_csums(trans, &ordered_extent->list);
    if (ret) {
        -->btrfs_abort_transaction(trans, ret);
        goto out;
    }

and the only thing that can fail in add_pending_csums is btrfs_csum_file_blocks. Which is why I said it points at this function.