| To: | Eric Sandeen <sandeen@xxxxxxxxxxx>, "Michael L. Semon" <mlsemon35@xxxxxxxxx>, çææ <yongtaofu@xxxxxxxxx> |
|---|---|
| Subject: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22 |
| From: | Ben Myers <bpm@xxxxxxx> |
| Date: | Tue, 9 Apr 2013 17:48:52 -0500 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <516493B3.5030106@xxxxxxxxxxx> |
| References: | <CADFMGuJm5bPPwbbUtYwrCVDL23KExJTw_-VRX2UEEdZjo+i5oA@xxxxxxxxxxxxxx> <CADFMGu+=MM2yc=_peboV7JTNJ8F05TJfexmEErzcf0D8mAWFRg@xxxxxxxxxxxxxx> <CAJzLF9k3f7ix7GD==26+JDg=5=AQWnJe3aopAHnQxXmzNPRkOw@xxxxxxxxxxxxxx> <516493B3.5030106@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
Hey, On Tue, Apr 09, 2013 at 05:18:27PM -0500, Eric Sandeen wrote: > On 4/9/13 5:16 PM, Michael L. Semon wrote: > > A meager non-expert user question with full ignorance of glusterfs: > > Why are you having I/O errors once every two weeks? > > It's runtime errors or corruption, followed by fs shutdown, which then > results in IO errors, because all IOs are rejected on the shutdown FS. > > But that's not always immediately obvious from the stream of resulting > "I/O Error" messages ;) The IO errors are maybe a bit excessive and scary. I can understand why some people might misinterpret those messages and assume it's a hardware problem. -Ben |
| Previous by Date: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, Eric Sandeen |
|---|---|
| Next by Date: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, Dave Chinner |
| Previous by Thread: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, Eric Sandeen |
| Next by Thread: | Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |