From: Chris J Arges <chris.j.arges@canonical.com>
To: xfs@oss.sgi.com
Subject: Re: Still seeing hangs in xlog_grant_log_space
Date: Wed, 6 Jun 2012 08:00:00 -0700 (PDT) [thread overview]
Message-ID: <33970511.post@talk.nabble.com> (raw)
In-Reply-To: <20120518101010.GW25351@dastard>
Dave Chinner wrote:
>
> It seems unlikely, but if you turn on kmemleak it might find a
> memory leak or overwrite that is causing this.
>
Running kmemleak on a 3.0.0 kernel results in the following:
dmesg:
[ 3855.751393] XFS (sda2): xlog_verify_grant_tail: space >
BBTOB(tail_blocks)
[22987.932317] kmemleak: 1 new suspected memory leaks (see
/sys/kernel/debug/kmemleak)
kmemleak:
unreferenced object 0xffff88015612a340 (size 208):
comm "copy-files", pid 1483, jiffies 4310560285 (age 16571.656s)
hex dump (first 32 bytes):
00 f3 1b 57 01 88 ff ff 00 08 00 58 01 88 ff ff ...W.......X....
a0 a7 32 a0 ff ff ff ff 04 00 00 00 00 00 00 00 ..2.............
backtrace:
[<ffffffff815c6196>] kmemleak_alloc+0x26/0x50
[<ffffffff811542e3>] kmem_cache_alloc+0x123/0x190
[<ffffffffa0313967>] kmem_zone_alloc+0x67/0xe0 [xfs]
[<ffffffffa03139fd>] kmem_zone_zalloc+0x1d/0x50 [xfs]
[<ffffffffa02b033f>] xfs_allocbt_init_cursor+0xdf/0x130 [xfs]
[<ffffffffa02adb4c>] xfs_alloc_ag_vextent_near+0x6c/0xd80 [xfs]
[<ffffffffa02aea88>] xfs_alloc_ag_vextent+0x228/0x290 [xfs]
[<ffffffffa02af7d9>] xfs_alloc_vextent+0x649/0x8c0 [xfs]
[<ffffffffa02bcfc6>] xfs_bmap_btalloc+0x286/0x7c0 [xfs]
[<ffffffffa02bd521>] xfs_bmap_alloc+0x21/0x40 [xfs]
[<ffffffffa02c6ba3>] xfs_bmapi+0xdc3/0x1950 [xfs]
[<ffffffffa02f5059>] xfs_iomap_write_allocate+0x179/0x340 [xfs]
[<ffffffffa03147d5>] xfs_map_blocks+0x215/0x380 [xfs]
[<ffffffffa0315792>] xfs_vm_writepage+0x1b2/0x510 [xfs]
[<ffffffff811142e7>] __writepage+0x17/0x40
[<ffffffff8111485d>] write_cache_pages+0x20d/0x460
analysis:
I turned on kmemleak, function tracing, and xfs debugging in the build
in which I ran this. So far I’ve been able to run the copy-files script for
about 24 hrs without failure. I’m not sure if this is because all these
features are turned on and it has slowed something down (so it takes longer
to reproduce), or if the debugging code is changing the behavior. I’m not
sure if this backtrace is valid, so I’m attaching an annotated objdump of my
xfs module.
--chris j arges
http://old.nabble.com/file/p33970511/xfs_objdump_3.0.txt.tar.bz2
xfs_objdump_3.0.txt.tar.bz2
--
View this message in context: http://old.nabble.com/Still-seeing-hangs-in-xlog_grant_log_space-tp33732886p33970511.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-06 15:00 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:09 Still seeing hangs in xlog_grant_log_space Juerg Haefliger
2012-04-23 14:38 ` Dave Chinner
2012-04-23 15:33 ` Juerg Haefliger
2012-04-23 23:58 ` Dave Chinner
2012-04-24 8:55 ` Juerg Haefliger
2012-04-24 12:07 ` Dave Chinner
2012-04-24 18:26 ` Juerg Haefliger
2012-04-25 22:38 ` Dave Chinner
2012-04-26 12:37 ` Juerg Haefliger
2012-04-26 22:44 ` Dave Chinner
2012-04-26 23:00 ` Juerg Haefliger
2012-04-26 23:07 ` Dave Chinner
2012-04-27 9:04 ` Juerg Haefliger
2012-04-27 11:09 ` Dave Chinner
2012-04-27 13:07 ` Juerg Haefliger
2012-05-05 7:44 ` Juerg Haefliger
2012-05-07 17:19 ` Ben Myers
2012-05-09 7:54 ` Juerg Haefliger
2012-05-10 16:11 ` Chris J Arges
2012-05-10 21:53 ` Mark Tinguely
2012-05-16 18:42 ` Ben Myers
2012-05-16 19:03 ` Chris J Arges
2012-05-16 21:29 ` Mark Tinguely
2012-05-18 10:10 ` Dave Chinner
2012-05-18 14:42 ` Mark Tinguely
2012-05-22 22:59 ` Dave Chinner
2012-06-06 15:00 ` Chris J Arges [this message]
2012-06-07 0:49 ` Dave Chinner
2012-05-17 20:55 ` Chris J Arges
2012-05-18 16:53 ` Chris J Arges
2012-05-18 17:19 ` Ben Myers
2012-05-19 7:28 ` Juerg Haefliger
2012-05-21 17:11 ` Ben Myers
2012-05-24 5:45 ` Juerg Haefliger
2012-05-24 14:23 ` Ben Myers
2012-05-07 22:59 ` Dave Chinner
2012-05-09 7:35 ` Dave Chinner
2012-05-09 21:07 ` Mark Tinguely
2012-05-10 2:10 ` Mark Tinguely
2012-05-18 9:37 ` Dave Chinner
2012-05-18 9:31 ` Dave Chinner
2012-05-24 20:18 ` Peter Watkins
2012-05-25 6:28 ` Juerg Haefliger
2012-05-25 17:03 ` Peter Watkins
2012-06-05 23:54 ` Dave Chinner
2012-06-06 13:40 ` Brian Foster
2012-06-06 17:41 ` Mark Tinguely
2012-06-11 20:42 ` Chris J Arges
2012-06-11 23:53 ` Dave Chinner
2012-06-12 13:28 ` Chris J Arges
2012-06-06 22:03 ` Mark Tinguely
2012-06-06 23:04 ` Brian Foster
2012-06-07 1:35 ` Dave Chinner
2012-06-07 14:16 ` Brian Foster
2012-06-08 0:28 ` Dave Chinner
2012-06-08 17:09 ` Ben Myers
2012-06-11 20:59 ` Mark Tinguely
2012-06-05 15:21 ` Chris J Arges
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=33970511.post@talk.nabble.com \
--to=chris.j.arges@canonical.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox