All of lore.kernel.org
 help / color / mirror / Atom feed
From: CAI Qian <caiqian@redhat.com>
To: xfs@oss.sgi.com, linux-xfs@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 3.8-rc5 xfs corruption
Date: Wed, 30 Jan 2013 22:16:47 -0500 (EST)	[thread overview]
Message-ID: <473604401.11548931.1359602207833.JavaMail.root@redhat.com> (raw)
In-Reply-To: <614607656.11545086.1359601991846.JavaMail.root@redhat.com>

Hello,

(Sorry to post to xfs mailing lists but unsure about which one is the
best for this.)

I have seen something like this once during testing on a system with a
EMC VNX FC/multipath back-end. Kernel config file is here,
http://people.redhat.com/qcai/stable/.config

[ 3025.063024] ffff8801a0d50000: 2e 2e 2f 2e 2e 2f 75 73 72 2f 6c 69 62 2f 6d 6f  ../../usr/lib/mo 
[ 3025.071743] XFS (dm-1): Internal error xfs_bmbt_verify at line 747 of file fs/xfs/xfs_bmap_btree.c.  Caller 0xffffffffa01c375e 
[ 3025.071743]  
[ 3025.084589] Pid: 275, comm: xfsaild/dm-1 Tainted: GF            3.8.0-rc5 #1 
[ 3025.091636] Call Trace: 
[ 3025.094176]  [<ffffffffa019910f>] xfs_error_report+0x3f/0x50 [xfs] 
[ 3025.100415]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.107163]  [<ffffffffa019917e>] xfs_corruption_error+0x5e/0x90 [xfs] 
[ 3025.113744]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.120495]  [<ffffffffa01c3606>] xfs_bmbt_verify+0x76/0x1c0 [xfs] 
[ 3025.126737]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.133481]  [<ffffffffa01975e5>] ? xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.139714]  [<ffffffffa01c375e>] xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.146287]  [<ffffffffa019713e>] _xfs_buf_ioapply+0x5e/0x370 [xfs] 
[ 3025.152565]  [<ffffffff81097c70>] ? try_to_wake_up+0x2d0/0x2d0 
[ 3025.158442]  [<ffffffffa01975e5>] ? xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.164669]  [<ffffffffa019752a>] xfs_buf_iorequest+0x4a/0xa0 [xfs] 
[ 3025.170979]  [<ffffffffa01975e5>] xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.177032]  [<ffffffffa01977c1>] __xfs_buf_delwri_submit+0x171/0x1e0 [xfs] 
[ 3025.184038]  [<ffffffffa0198110>] ? xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs] 
[ 3025.191491]  [<ffffffffa01f1100>] ? xfs_trans_ail_cursor_first+0x80/0xb0 [xfs] 
[ 3025.198755]  [<ffffffffa0198110>] xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs] 
[ 3025.206030]  [<ffffffffa01f1352>] xfsaild+0x222/0x5e0 [xfs] 
[ 3025.211665]  [<ffffffffa01f1130>] ? xfs_trans_ail_cursor_first+0xb0/0xb0 [xfs] 
[ 3025.218890]  [<ffffffff81085b10>] kthread+0xc0/0xd0 
[ 3025.223784]  [<ffffffff81085a50>] ? kthread_create_on_node+0x120/0x120 
[ 3025.230317]  [<ffffffff816176ec>] ret_from_fork+0x7c/0xb0 
[ 3025.235721]  [<ffffffff81085a50>] ? kthread_create_on_node+0x120/0x120 
[ 3025.242248] XFS (dm-1): Corruption detected. Unmount and run xfs_repair 
[ 3025.248865] XFS (dm-1): xfs_do_force_shutdown(0x8) called from line 1340 of file fs/xfs/xfs_buf.c.  Return address = 0xffffffffa0197411 

Does this ring any bell?

Regards,
CAI Qian

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: CAI Qian <caiqian@redhat.com>
To: xfs@oss.sgi.com, linux-xfs@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 3.8-rc5 xfs corruption
Date: Wed, 30 Jan 2013 22:16:47 -0500 (EST)	[thread overview]
Message-ID: <473604401.11548931.1359602207833.JavaMail.root@redhat.com> (raw)
In-Reply-To: <614607656.11545086.1359601991846.JavaMail.root@redhat.com>

Hello,

(Sorry to post to xfs mailing lists but unsure about which one is the
best for this.)

I have seen something like this once during testing on a system with a
EMC VNX FC/multipath back-end. Kernel config file is here,
http://people.redhat.com/qcai/stable/.config

[ 3025.063024] ffff8801a0d50000: 2e 2e 2f 2e 2e 2f 75 73 72 2f 6c 69 62 2f 6d 6f  ../../usr/lib/mo 
[ 3025.071743] XFS (dm-1): Internal error xfs_bmbt_verify at line 747 of file fs/xfs/xfs_bmap_btree.c.  Caller 0xffffffffa01c375e 
[ 3025.071743]  
[ 3025.084589] Pid: 275, comm: xfsaild/dm-1 Tainted: GF            3.8.0-rc5 #1 
[ 3025.091636] Call Trace: 
[ 3025.094176]  [<ffffffffa019910f>] xfs_error_report+0x3f/0x50 [xfs] 
[ 3025.100415]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.107163]  [<ffffffffa019917e>] xfs_corruption_error+0x5e/0x90 [xfs] 
[ 3025.113744]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.120495]  [<ffffffffa01c3606>] xfs_bmbt_verify+0x76/0x1c0 [xfs] 
[ 3025.126737]  [<ffffffffa01c375e>] ? xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.133481]  [<ffffffffa01975e5>] ? xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.139714]  [<ffffffffa01c375e>] xfs_bmbt_write_verify+0xe/0x10 [xfs] 
[ 3025.146287]  [<ffffffffa019713e>] _xfs_buf_ioapply+0x5e/0x370 [xfs] 
[ 3025.152565]  [<ffffffff81097c70>] ? try_to_wake_up+0x2d0/0x2d0 
[ 3025.158442]  [<ffffffffa01975e5>] ? xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.164669]  [<ffffffffa019752a>] xfs_buf_iorequest+0x4a/0xa0 [xfs] 
[ 3025.170979]  [<ffffffffa01975e5>] xfs_bdstrat_cb+0x65/0xd0 [xfs] 
[ 3025.177032]  [<ffffffffa01977c1>] __xfs_buf_delwri_submit+0x171/0x1e0 [xfs] 
[ 3025.184038]  [<ffffffffa0198110>] ? xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs] 
[ 3025.191491]  [<ffffffffa01f1100>] ? xfs_trans_ail_cursor_first+0x80/0xb0 [xfs] 
[ 3025.198755]  [<ffffffffa0198110>] xfs_buf_delwri_submit_nowait+0x20/0x30 [xfs] 
[ 3025.206030]  [<ffffffffa01f1352>] xfsaild+0x222/0x5e0 [xfs] 
[ 3025.211665]  [<ffffffffa01f1130>] ? xfs_trans_ail_cursor_first+0xb0/0xb0 [xfs] 
[ 3025.218890]  [<ffffffff81085b10>] kthread+0xc0/0xd0 
[ 3025.223784]  [<ffffffff81085a50>] ? kthread_create_on_node+0x120/0x120 
[ 3025.230317]  [<ffffffff816176ec>] ret_from_fork+0x7c/0xb0 
[ 3025.235721]  [<ffffffff81085a50>] ? kthread_create_on_node+0x120/0x120 
[ 3025.242248] XFS (dm-1): Corruption detected. Unmount and run xfs_repair 
[ 3025.248865] XFS (dm-1): xfs_do_force_shutdown(0x8) called from line 1340 of file fs/xfs/xfs_buf.c.  Return address = 0xffffffffa0197411 

Does this ring any bell?

Regards,
CAI Qian

       reply	other threads:[~2013-01-31  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <614607656.11545086.1359601991846.JavaMail.root@redhat.com>
2013-01-31  3:16 ` CAI Qian [this message]
2013-01-31  3:16   ` 3.8-rc5 xfs corruption CAI Qian
2013-01-31  4:07   ` Dave Chinner
2013-01-31  4:07     ` Dave Chinner
2013-01-31  8:01     ` CAI Qian
2013-01-31  8:01       ` CAI Qian

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=473604401.11548931.1359602207833.JavaMail.root@redhat.com \
    --to=caiqian@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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 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.