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:23:40 -0500 [thread overview]
Message-ID: <5164327C.6060808@sandeen.net> (raw)
In-Reply-To: <CADFMGuL7968v6L-3=j3FY3YYjeA_XH1CyuLgnL88u-abxiwHvg@mail.gmail.com>
On 4/9/13 10:18 AM, 符永涛 wrote:
> The servers are back to service now and It's hard to run xfs_repair.
> It always happen bellow is the xfs_repair log when it happens on
> another server several days ago.
> -sh-4.1$ sudo xfs_repair -n /dev/glustervg/glusterlv
Ok; just for what its worth, if you don't mount/umount first,
you may be running repair -n with a dirty log, and it will
find "more" corruption than it should, since the log is not
replayed.
I see that you included a non "-n" repair log as well, was
that after a mount/umount? Just to be sure...
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-09 15:23 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
2013-04-09 15:18 ` 符永涛
2013-04-09 15:23 ` Eric Sandeen [this message]
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=5164327C.6060808@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