On Mon, Jan 21, 2013 at 05:01:36PM +1100, Skender wrote:
> I noticed in the dmesg logs that there seems to be a bug/issue with btrfs.
> Here is the trace/message from dmesg. Im going by the instructions from
> the
> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#How_do_I_report_bugs_and_issues.3F
> . Let me know if you need anything else.
Please paste a few lines around the messages, the error code is missing,
though I'm suspecting it to be ENOSPC:
submit_compressed_extents:
659 if (IS_ERR(trans)) {
660 ret = PTR_ERR(trans);
661 } else {
662 trans->block_rsv =
&root->fs_info->delalloc_block_rsv;
663 ret = btrfs_reserve_extent(trans, root,
664 async_extent->compressed_size,
665 async_extent->compressed_size,
666 0, alloc_hint, &ins, 1);
667 if (ret)
668 btrfs_abort_transaction(trans, root, ret);
(here it aborts)
669 btrfs_end_transaction(trans, root);
670 }
I've never seen this error before.
david
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
