From: Ben Myers <bpm@sgi.com>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs fails in xfstests 013
Date: Thu, 31 Jan 2013 13:08:26 -0600 [thread overview]
Message-ID: <20130131190826.GQ27055@sgi.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1301310910080.14328@dhcp-1-104.brq.redhat.com>
Hey Lukas,
On Thu, Jan 31, 2013 at 09:19:23AM +0100, Lukáš Czerner wrote:
> I've just run xfstest 013 on xfs and it fails with this backtrace
>
>
> Jan 31 03:09:07 rhel6_vm1 kernel: ffff88020b6d1000: 78 78 78 78 78 78 78 78 78 78 2f 78 78 78 78 78 xxxxxxxxxx/xxxxx
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): Internal error xfs_bmbt_verify at line 747 of file fs/xfs/xfs_bmap_btree.c. Caller 0xffffffffa025486e
> Jan 31 03:09:07 rhel6_vm1 kernel:
> Jan 31 03:09:07 rhel6_vm1 kernel: Pid: 8909, comm: xfsaild/sda Tainted: GF 3.8.0-rc5-orig+ #8
> Jan 31 03:09:07 rhel6_vm1 kernel: Call Trace:
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa022877f>] xfs_error_report+0x3f/0x50 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa025486e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02287ee>] xfs_corruption_error+0x5e/0x90 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa0254710>] xfs_bmbt_verify+0x80/0x1d0 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa025486e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa025486e>] xfs_bmbt_write_verify+0xe/0x10 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02269a5>] _xfs_buf_ioapply+0x65/0x150 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffff8108d170>] ? try_to_wake_up+0x2b0/0x2b0
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02270a5>] ? xfs_bdstrat_cb+0x65/0xd0 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa0226fef>] xfs_buf_iorequest+0x4f/0xa0 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02270a5>] xfs_bdstrat_cb+0x65/0xd0 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa0227218>] __xfs_buf_delwri_submit+0x108/0x200 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02273c0>] ? xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02273c0>] xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa0282376>] xfsaild_push+0x1b6/0x520 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa0282778>] xfsaild+0x98/0x130 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffffa02826e0>] ? xfsaild_push+0x520/0x520 [xfs]
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffff8107968e>] kthread+0xce/0xe0
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffff810795c0>] ? kthread_freezable_should_stop+0x70/0x70
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffff8155cdec>] ret_from_fork+0x7c/0xb0
> Jan 31 03:09:07 rhel6_vm1 kernel: [<ffffffff810795c0>] ? kthread_freezable_should_stop+0x70/0x70
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): Corruption detected. Unmount and run xfs_repair
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): xfs_do_force_shutdown(0x8) called from line 1358 of file fs/xfs/xfs_buf.c. Return address = 0xffffffffa0226a85
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): Corruption of in-memory data detected. Shutting down filesystem
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): Please umount the filesystem and rectify the problem(s)
> Jan 31 03:09:07 rhel6_vm1 kernel: XFS (sda): xfs_log_force: error 5 returned.
>
>
> I can reproduce it every time with xfstest 013 on 3.8.0-rc5.
I haven't been able to reproduce this with test 013. Could you grab a
metadump?
Thanks,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-01-31 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 8:19 Xfs fails in xfstests 013 Lukáš Czerner
2013-01-31 19:08 ` Ben Myers [this message]
2013-02-01 0:29 ` Dave Chinner
2013-02-01 10:58 ` Lukáš Czerner
2013-02-01 14:33 ` Lukáš Czerner
2013-02-03 23:00 ` Dave Chinner
2013-02-10 22:16 ` Dave Chinner
2013-02-11 12:08 ` Lukáš Czerner
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=20130131190826.GQ27055@sgi.com \
--to=bpm@sgi.com \
--cc=lczerner@redhat.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