From: Michael Weissenbacher <mw@dermichi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: XFS hang during xfs_fsr run
Date: Sat, 06 Mar 2010 22:20:28 +0100 [thread overview]
Message-ID: <4B92C71C.5010003@dermichi.com> (raw)
In-Reply-To: <20100304222611.GK14317@discord.disaster>
> If xfs_fsr hung before it checked the nodefrag flag, then there's
> only a few things it could get stuck on:
>
> 1. fsync() of the file
> 2. file lock checks
> 3. statvfs64()
> 4. ioctl(XFS_IOC_FSGETXATTR)
>
> A trace would tell us which one it was....
>
Got another one, this time with ksyms enabled:
[192115.749003] BUG: unable to handle kernel NULL pointer dereference at
0000000000000018
[192115.749197] IP: [<ffffffff811ad69d>] xfs_trans_find_item+0x1/0xa
[192115.749259] PGD 2f0dec067 PUD 1b1ab9067 PMD 0
[192115.749264] Oops: 0000 [#1] SMP
[192115.749267] last sysfs file:
/sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
[192115.749271] CPU 3
[192115.749276] Pid: 1671, comm: xfs_fsr Not tainted 2.6.33 #1
0JR815/PowerEdge 2950
[192115.749279] RIP: 0010:[<ffffffff811ad69d>] [<ffffffff811ad69d>]
xfs_trans_find_item+0x1/0xa
[192115.749284] RSP: 0018:ffff8800aec13b78 EFLAGS: 00010296
[192115.749287] RAX: 0000000000000008 RBX: ffff8800ad600320 RCX:
ffff8800aec13d54
[192115.749289] RDX: 0000000000000005 RSI: 0000000000000000 RDI:
ffff8800ad600320
[192115.749292] RBP: ffff8800aec13ba8 R08: 000000000000007c R09:
ffff88032fb0b600
[192115.749295] R10: 00000000ffffffff R11: ffff8800282cde60 R12:
ffff8802d3f12c00
[192115.749298] R13: 0000000000000005 R14: 0000000000000000 R15:
ffff8802d3f12c38
[192115.749302] FS: 00007f8f3cc5a6f0(0000) GS:ffff8800282c0000(0000)
knlGS:0000000000000000
[192115.749305] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[192115.749307] CR2: 0000000000000018 CR3: 000000014904b000 CR4:
00000000000006e0
[192115.749310] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[192115.749313] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[192115.749316] Process xfs_fsr (pid: 1671, threadinfo ffff8800aec12000,
task ffff88032e77b600)
[192115.749318] Stack:
[192115.749320] ffff8800aec13ba8 ffffffff811ad5c0 ffff8802d3f12c00
0000000000000000
[192115.749324] <0> ffff8802d3f12c00 ffffffffffffffff ffff8800aec13ce8
ffffffff81180554
[192115.749328] <0> ffff8800aec13ca8 0000000000000000 ffff880000000000
ffff880300000000
[192115.749332] Call Trace:
[192115.749338] [<ffffffff811ad5c0>] ? xfs_trans_log_inode+0x22/0x4c
[192115.749344] [<ffffffff81180554>] xfs_bunmapi+0x9ec/0xa36
[192115.749350] [<ffffffff8119a452>] xfs_itruncate_finish+0x188/0x2db
[192115.749355] [<ffffffff811b0d41>] xfs_inactive+0x218/0x435
[192115.749360] [<ffffffff81364338>] ? __mutex_lock_slowpath+0x22d/0x23c
[192115.749365] [<ffffffff811bb096>] xfs_fs_clear_inode+0xb3/0xb8
[192115.749371] [<ffffffff810df28a>] clear_inode+0x78/0xd1
[192115.749375] [<ffffffff810df9f8>] generic_delete_inode+0xf6/0x16b
[192115.749379] [<ffffffff810dfa84>] generic_drop_inode+0x17/0x62
[192115.749382] [<ffffffff810deace>] iput+0x61/0x65
[192115.749386] [<ffffffff810dbf25>] dentry_iput+0xb5/0xc5
[192115.749389] [<ffffffff810dc00f>] d_kill+0x43/0x63
[192115.749393] [<ffffffff810dc75f>] dput+0x148/0x155
[192115.749398] [<ffffffff810cda56>] __fput+0x196/0x1bb
[192115.749401] [<ffffffff810cda93>] fput+0x18/0x1a
[192115.749405] [<ffffffff810cac36>] filp_close+0x67/0x72
[192115.749409] [<ffffffff810cacda>] sys_close+0x99/0xd2
[192115.749415] [<ffffffff810029ab>] system_call_fastpath+0x16/0x1b
[192115.749417] Code: 89 c4 85 c0 75 13 48 85 db 74 0e 44 89 ea 49 8b 36
48 89 df e8 5f ff ff ff 5a 44 89 e0 59 5b 41 5c 41 5d 41 5e c9 c3 90 90
90 55 <48> 8b 46 18 48 89 e5 c9 c3 55 31 ff 8a 56 0b 48 89 e5 0f b6 c2
[192115.749441] RIP [<ffffffff811ad69d>] xfs_trans_find_item+0x1/0xa
[192115.749445] RSP <ffff8800aec13b78>
[192115.749447] CR2: 0000000000000018
[192115.749458] ---[ end trace b5b512ceb91c24c7 ]---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-06 21:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 10:10 XFS hang during xfs_fsr run Michael Weissenbacher
2010-03-04 11:20 ` Dave Chinner
2010-03-04 12:08 ` Michael Weissenbacher
2010-03-04 13:15 ` Dave Chinner
2010-03-04 13:46 ` Christoph Hellwig
2010-03-04 14:20 ` Michael Weissenbacher
2010-03-04 14:30 ` Christoph Hellwig
2010-03-04 17:14 ` Michael Weissenbacher
2010-03-04 22:26 ` Dave Chinner
2010-03-05 9:04 ` Michael Weissenbacher
2010-03-06 21:20 ` Michael Weissenbacher [this message]
2010-03-08 0:06 ` Dave Chinner
2010-03-08 12:17 ` Michael Weissenbacher
2010-03-08 18:09 ` Eric Sandeen
2010-03-09 9:14 ` Michael Weissenbacher
2010-03-09 11:38 ` Dave Chinner
2010-03-09 12:09 ` Michael Weissenbacher
2010-03-10 8:46 ` Michael Weissenbacher
2010-03-11 23:39 ` Dave Chinner
2010-03-12 9:45 ` Michael Weissenbacher
2010-03-12 10:00 ` Christoph Hellwig
2010-03-12 10:36 ` Michael Weissenbacher
2010-03-12 11:56 ` Dave Chinner
2010-03-12 14:27 ` Christoph Hellwig
2010-03-13 0:25 ` Dave Chinner
2010-04-16 8:10 ` Michael Monnerie
2010-04-16 10:50 ` Michael Weissenbacher
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=4B92C71C.5010003@dermichi.com \
--to=mw@dermichi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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