From: Josef Bacik <jbacik@fb.com>
To: Sage Weil <sage@inktank.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: warn at fs/btrfs/extent-tree.c:5748 __btrfs_free_extent+0x9ce/0xa20
Date: Fri, 14 Mar 2014 11:35:49 -0400 [thread overview]
Message-ID: <532321D5.4020906@fb.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1403140832510.316@cobra.newdream.net>
On 03/14/2014 11:34 AM, Sage Weil wrote:
> On Fri, 14 Mar 2014, Josef Bacik wrote:
>> On 03/11/2014 07:44 PM, Sage Weil wrote:
>>> Hey,
>>>
>>> Is this something you guys have seen before? This is from v3.13-rc2.
>>>
>>> kernel: [49432.696440] WARNING: CPU: 3 PID: 26411 at /srv/autobuild-ceph/gitbuilder.git/build/fs/btrfs/extent-tree.c:5748 __btrfs_free_extent+0x9ce/0xa20 [btrfs]()
>>> kernel: [49432.710128] Modules linked in: arc4(F) md4(F) nls_utf8(F) cifs(F) ufs(F) qnx4(F) hfsplus(F) hfs(F) minix(F) ntfs(F) msdos(F) jfs(F) xfs(F) reiserfs(F) ext2(F) kvm_intel(F) kvm(F) ib_iser(F) rdma_cm(F) ib_cm(F) iw_cm(F) ib_sa(F) ib_mad(F) ib_core(F) ib_addr(F) iscsi_tcp(F) libiscsi_tcp(F) libiscsi(F) psmouse(F) ipmi_si(F) serio_raw(F) gpio_ich(F) joydev(F) dcdbas(F) i7core_edac(F) edac_core(F) ipmi_msghandler(F) mac_hid(F) acpi_power_meter(F) lpc_ich(F) tpm_tis(F) nfsd(F) nfs_acl(F) auth_rpcgss(F) scsi_transport_iscsi(F) nfs(F) fscache(F) lockd(F) lp(F) sunrpc(F) parport(F) hid_generic(F) usbhid(F) hid(F) btrfs(F) raid6_pq(F) mptsas(F) ixgbe(F) mptscsih(F) dca(F) mptbase(F) ptp(F) pps_core(F) scsi_transport_sas(F) xor(F) mdio(F) bnx2(F) libcrc32c(F)
>>> kernel: [49432.777445] CPU: 3 PID: 26411 Comm: ceph-osd Tainted: GF I 3.14.0-rc5-ceph-00016-gf31a96a #1
>>> kernel: [49432.786704] Hardware name: Dell Inc. PowerEdge R410/01V648, BIOS 1.6.3 02/07/2011
>>> kernel: [49432.794223] 0000000000001674 ffff8800bf1cbac8 ffffffff816e4840 ffff88022726ef90
>>> kernel: [49432.801700] 0000000000000000 ffff8800bf1cbb08 ffffffff810524ac a800000000b07e50
>>> kernel: [49432.809176] ffff880094e74120 0000000000000000 00000000b07c9000 0000000000000000
>>> kernel: [49432.816653] Call Trace:
>>> kernel: [49432.819119] [<ffffffff816e4840>] dump_stack+0x46/0x58
>>> kernel: [49432.825384] [<ffffffff810524ac>] warn_slowpath_common+0x8c/0xc0
>>> kernel: [49432.831413] [<ffffffff810524fa>] warn_slowpath_null+0x1a/0x20
>>> kernel: [49432.837284] [<ffffffffa010b4be>] __btrfs_free_extent+0x9ce/0xa20 [btrfs]
>>> kernel: [49432.844108] [<ffffffffa01110b8>] __btrfs_run_delayed_refs+0x428/0x11e0 [btrfs]
>>> kernel: [49432.851465] [<ffffffffa0109458>] ? block_rsv_release_bytes+0x108/0x190 [btrfs]
>>> kernel: [49432.858823] [<ffffffffa0114066>] btrfs_run_delayed_refs+0x76/0x2a0 [btrfs]
>>> kernel: [49432.865869] [<ffffffffa01251ff>] __btrfs_end_transaction+0x26f/0x370 [btrfs]
>>> kernel: [49432.873044] [<ffffffffa0125330>] btrfs_end_transaction+0x10/0x20 [btrfs]
>>> kernel: [49432.879872] [<ffffffffa01327de>] btrfs_link+0x13e/0x1d0 [btrfs]
>>> kernel: [49432.885903] [<ffffffff811b7571>] vfs_link+0x1b1/0x270
>>> kernel: [49432.891060] [<ffffffff811b8120>] SyS_linkat+0x210/0x2d0
>>> kernel: [49432.896394] [<ffffffff811b81fe>] SyS_link+0x1e/0x20
>>> kernel: [49432.901380] [<ffffffff816f7cd6>] system_call_fastpath+0x1a/0x1f
>>>
>>> The full dump is at
>>>
>>> https://urldefense.proofpoint.com/v1/url?u=http://tracker.ceph.com/issues/7688&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cKCbChRKsMpTX8ybrSkonQ%3D%3D%0A&m=5Q0Wl4GGvXb3sw11Xy%2FYQnZbcMlzHHsbegI1uoQnEbE%3D%0A&s=f85b1094d776c10386c681a8a7b31e49f0621bf51829b6e7153095f2335a01c0
>>> https://urldefense.proofpoint.com/v1/url?u=http://tracker.ceph.com/attachments/download/1141/kern.log.gz&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cKCbChRKsMpTX8ybrSkonQ%3D%3D%0A&m=5Q0Wl4GGvXb3sw11Xy%2FYQnZbcMlzHHsbegI1uoQnEbE%3D%0A&s=dff103270aba751a919e566182a4d9482041f972ac72cb12435814ae75cacf14
>>>
>>
>> Filipe's looking at this Sage, you said it happend on v3.13-rc2 but the
>> kernel line says 3.14.0-rc5, have you had it happen in both places? Thanks,
>
> Whoops, that's my mistake.. it's 3.14-rc5. The exact commit is it
> git://github.com/ceph/ceph-client.git, if it matters; it's -rc5 + some
> ceph patches.
>
Cool, not worried about what you guys are doing, just wondering if it
may be related to me screwing around in delayed ref land recently or if
you had seen it earlier too. Thanks,
Josef
next prev parent reply other threads:[~2014-03-14 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 23:44 warn at fs/btrfs/extent-tree.c:5748 __btrfs_free_extent+0x9ce/0xa20 Sage Weil
2014-03-12 7:54 ` Duncan
2014-03-14 15:27 ` Josef Bacik
2014-03-14 15:34 ` Sage Weil
2014-03-14 15:35 ` Josef Bacik [this message]
2014-03-14 15:52 ` Filipe David Manana
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=532321D5.4020906@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@inktank.com \
/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.