public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: 符永涛 <yongtaofu@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22
Date: Tue, 09 Apr 2013 10:06:06 -0500	[thread overview]
Message-ID: <51642E5E.3040403@sandeen.net> (raw)
In-Reply-To: <CADFMGuJm5bPPwbbUtYwrCVDL23KExJTw_-VRX2UEEdZjo+i5oA@mail.gmail.com>

On 4/9/13 7:53 AM, 符永涛 wrote:
> Dear xfs experts,
> I really need your help sincerely!!! In our production enviroment we
> run glusterfs over top of xfs on Dell x720D(Raid 6). And the xfs file
> system crash on some of the server frequently about every two weeks.
> Can you help to give me a direction about how to debug this issue and
> how to avoid it? Thank you very very much!

So this happens reliably, but infrequently? (only every 2 weeks or so?)

Can you provoke it any more often?

> uname -a
> Linux cqdx.miaoyan.cluster1.node11.qiyi.domain 2.6.32-279.el6.x86_64
> #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

That's a RHEL6 kernel; I'm assuming that this is a RHEL clone w/o RH support?

I agree with Ben that I'd like to see xfs_repair output.

Since the fs has shut down, you should unmount, remount, and unmount
again to replay the dirty log.  Then do xfs_repair -n, and provide the output
if it discovers any errors.

Thanks,
-Eric

> Every time the crash log is same, as following
> 
> 038 Apr  9 09:41:36 cqdx kernel: XFS (sdb): xfs_iunlink_remove:
> xfs_inotobp() returned error 22.
> 1039 Apr  9 09:41:36 cqdx kernel: XFS (sdb): xfs_inactive: xfs_ifree
> returned error 22
> 1040 Apr  9 09:41:36 cqdx kernel: XFS (sdb):
> xfs_do_force_shutdown(0x1) called from line 1184 of file
> fs/xfs/xfs_vnodeops.c.  Return address = 0xffffffffa02ee20a
> 1041 Apr  9 09:41:36 cqdx kernel: XFS (sdb): I/O Error Detected.
> Shutting down filesystem
> 1042 Apr  9 09:41:36 cqdx kernel: XFS (sdb): Please umount the
> filesystem and rectify the problem(s)
> 1043 Apr  9 09:41:53 cqdx kernel: XFS (sdb): xfs_log_force: error 5 returned.
> 1044 Apr  9 09:42:23 cqdx kernel: XFS (sdb): xfs_log_force: error 5 returned.
> 1045 Apr  9 09:42:53 cqdx kernel: XFS (sdb): xfs_log_force: error 5 returned.
> 1046 Apr  9 09:43:23 cqdx kernel: XFS (sdb): xfs_log_force: error 5 returned.
> 

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

  parent reply	other threads:[~2013-04-09 15:06 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 12:53 need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22 符永涛
2013-04-09 13:03 ` 符永涛
2013-04-09 13:05   ` 符永涛
2013-04-09 14:52     ` Ben Myers
2013-04-09 15:00       ` 符永涛
2013-04-09 15:07       ` 符永涛
2013-04-09 15:10         ` 符永涛
2013-04-10 10:10           ` Emmanuel Florac
2013-04-10 12:52             ` Dave Chinner
2013-04-10 13:52             ` 符永涛
2013-04-11 19:11               ` 符永涛
2013-04-11 19:55                 ` 符永涛
2013-04-11 23:26                 ` Brian Foster
2013-04-12  0:45                   ` 符永涛
2013-04-12 12:50                     ` Brian Foster
2013-04-12 13:42                       ` 符永涛
2013-04-12 13:48                         ` 符永涛
2013-04-12 13:51                           ` 符永涛
2013-04-12 13:59                             ` 符永涛
2013-04-12  1:07                   ` Eric Sandeen
2013-04-12  1:36                     ` 符永涛
2013-04-12  1:38                       ` 符永涛
2013-04-12  6:15                     ` 符永涛
2013-04-12  4:32                   ` 符永涛
2013-04-12  5:16                     ` Eric Sandeen
2013-04-12  5:40                       ` 符永涛
2013-04-12  6:00                         ` 符永涛
2013-04-12 12:11                           ` Brian Foster
2013-04-12  7:44                         ` 符永涛
2013-04-12  8:32                           ` 符永涛
2013-04-12 12:41                             ` Brian Foster
2013-04-12 14:48                               ` 符永涛
2013-04-15  2:08                                 ` 符永涛
2013-04-15  5:04                                   ` 符永涛
2013-04-15 12:54                                     ` 符永涛
2013-04-15 13:33                                       ` 符永涛
2013-04-15 13:36                                         ` 符永涛
2013-04-15 13:45                                           ` 符永涛
2013-04-15 13:57                                             ` Eric Sandeen
2013-04-15 14:21                                               ` 符永涛
2013-04-15 15:24                                                 ` 符永涛
2013-04-15 19:34                                                 ` Eric Sandeen
2013-04-15 14:13                                       ` Brian Foster
2013-04-12  5:23                     ` 符永涛
2013-04-09 22:16   ` Michael L. Semon
2013-04-09 22:18     ` Eric Sandeen
2013-04-09 22:48       ` Ben Myers
2013-04-09 23:30         ` Dave Chinner
2013-04-09 15:06 ` Eric Sandeen [this message]
2013-04-09 15:18   ` 符永涛
2013-04-09 15:23     ` Eric Sandeen
2013-04-09 15:25       ` 符永涛
2013-04-09 15:23     ` 符永涛
2013-04-09 15:44       ` Eric Sandeen
2013-04-09 15:48         ` 符永涛
2013-04-09 15:49           ` 符永涛
2013-04-09 15:58           ` Brian Foster
2013-04-09 17:10     ` Eric Sandeen
2013-04-10  5:34       ` 符永涛
2013-04-10  5:36         ` 符永涛

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=51642E5E.3040403@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    --cc=yongtaofu@gmail.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