From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q0V1Vd04169666 for ; Mon, 30 Jan 2012 19:31:40 -0600 Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by cuda.sgi.com with ESMTP id lo7CEouAzJwLdrRx for ; Mon, 30 Jan 2012 17:31:37 -0800 (PST) Date: Tue, 31 Jan 2012 12:31:24 +1100 From: Dave Chinner Subject: Re: File system remain unresponsive until the system is rebooted. Message-ID: <20120131013124.GE9090@dastard> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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 Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Supratik Goswami Cc: xfs@oss.sgi.com On Mon, Jan 30, 2012 at 02:48:58PM +0530, Supratik Goswami wrote: > Hi > > We are using RAID-0 volumes as PV's in our LVM stack and XFS as the filesystem. > > The kernel logged the below call trace when the filesystem was being > expanded using "xfs_growfs" command. > We have used xfs_grofs at least 3 times earlier but did not cam across > this situation. > > The files system remained unresponsive until we rebooted the system > and again increased the size of the filesystem. > This time it worked fine. Can you please tell us why xfs_grofs hanged suddenly ? What kernel? Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs