| To: | 符永涛 <yongtaofu@xxxxxxxxx> |
|---|---|
| Subject: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 09 Apr 2013 10:23:40 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CADFMGuL7968v6L-3=j3FY3YYjeA_XH1CyuLgnL88u-abxiwHvg@xxxxxxxxxxxxxx> |
| References: | <CADFMGuJm5bPPwbbUtYwrCVDL23KExJTw_-VRX2UEEdZjo+i5oA@xxxxxxxxxxxxxx> <51642E5E.3040403@xxxxxxxxxxx> <CADFMGuL7968v6L-3=j3FY3YYjeA_XH1CyuLgnL88u-abxiwHvg@xxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 |
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 |
| Previous by Date: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, 符永涛 |
|---|---|
| Next by Date: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, 符永涛 |
| Previous by Thread: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, 符永涛 |
| Next by Thread: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, 符永涛 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |