From: Skender <skender@gmail.com>
To: David Sterba <dsterba@suse.cz>
Cc: Skender <skender@gmail.com>,
linux-btrfs@vger.kernel.org, jbacik@fusionio.com
Subject: Re: BTRFS dmesg error
Date: Tue, 22 Jan 2013 07:20:17 +1100 [thread overview]
Message-ID: <20130121202016.GA24179@blackspider> (raw)
In-Reply-To: <20130121110026.GE19967@twin.jikos.cz>
Here are a couple of lines before and after.
Cheers,
Skender Haxhimolla
[432770.724678] virtuoso-t[17472]: segfault at 8 ip 00000000007f4147 sp 00007fff69250848 error 4 in virtuoso-t[400000+9ad000]
[615597.825359] mythtranscode[10886]: segfault at 4 ip 00000000004243c9 sp 00007fff27970368 error 4 in mythtranscode[400000+68000]
[655330.131113] ------------[ cut here ]------------
[655330.131123] WARNING: at fs/btrfs/super.c:246 __btrfs_abort_transaction+0x46/0xa0()
[655330.131125] Hardware name: Precision WorkStation T3400
[655330.131126] btrfs: Transaction aborted
[655330.131128] Modules linked in: xt_limit xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm bnep bluetooth dm_crypt dvb_usb_cxusb snd_hda_codec_analog dib7000p dibx000_common dvb_usb snd_hda_intel snd_hda_codec snd_hwdep dvb_core snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event rc_core dib0070 snd_seq coretemp snd_timer snd_seq_device snd kvm_intel soundcore kvm psmouse snd_page_alloc microcode x38_edac lpc_ich dcdbas serio_raw edac_core ppdev parport_pc lp parport floppy firewire_ohci firewire_core crc_itu_t nouveau tg3 ttm drm_kms_helper drm i2c_algo_bit mxm_wmi video wmi
[655330.131182] Pid: 5838, comm: btrfs-delalloc- Not tainted 3.6.11-custom #1
[655330.131183] Call Trace:
[655330.131190] [<ffffffff810507dc>] warn_slowpath_common+0x83/0x9c
[655330.131193] [<ffffffff81050898>] warn_slowpath_fmt+0x46/0x48
[655330.131197] [<ffffffff81231e0b>] ? btrfs_reserve_extent+0xbd/0x1c6
[655330.131200] [<ffffffff812208a7>] __btrfs_abort_transaction+0x46/0xa0
[655330.131203] [<ffffffff812468f4>] submit_compressed_extents+0x1bd/0x415
[655330.131207] [<ffffffff81246bd2>] async_cow_submit+0x86/0x8b
[655330.131210] [<ffffffff8125ec27>] run_ordered_completions+0x76/0xd5
[655330.131213] [<ffffffff8125f49e>] worker_loop+0x183/0x4b9
[655330.131216] [<ffffffff8125f31b>] ? btrfs_queue_worker+0x288/0x288
[655330.131220] [<ffffffff8106d9d0>] kthread+0x6f/0x77
[655330.131225] [<ffffffff815b59c4>] kernel_thread_helper+0x4/0x10
[655330.131228] [<ffffffff8106d961>] ? kthread_freezable_should_stop+0x48/0x48
[655330.131231] [<ffffffff815b59c0>] ? gs_change+0x13/0x13
[655330.131233] ---[ end trace bc2b68accbd79b9c ]---
[655330.131235] BTRFS warning (device sda2): Aborting unused transaction.
[655729.210531] BTRFS warning (device sda2): Aborting unused transaction.
On 21/01/13 12:00 +0100, David Sterba wrote:
> 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
next prev parent reply other threads:[~2013-01-21 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 6:01 BTRFS dmesg error Skender
2013-01-21 11:00 ` David Sterba
2013-01-21 20:20 ` Skender [this message]
2013-01-22 14:17 ` David Sterba
2013-01-22 21:41 ` Skender
2013-01-23 16:30 ` David Sterba
2013-01-23 20:34 ` Skender
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130121202016.GA24179@blackspider \
--to=skender@gmail.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.