From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 093747FA5 for ; Tue, 9 Apr 2013 17:48:53 -0500 (CDT) Date: Tue, 9 Apr 2013 17:48:52 -0500 From: Ben Myers Subject: Re: need help how to debug xfs crash issue xfs_iunlink_remove: xfs_inotobp() returned error 22 Message-ID: <20130409224852.GF22182@sgi.com> References: <516493B3.5030106@sandeen.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <516493B3.5030106@sandeen.net> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Eric Sandeen , "Michael L. Semon" , =?utf-8?B?56ym5rC45rab?= Cc: "xfs@oss.sgi.com" 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 _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs