Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266333AbUAGSXq (ORCPT ); Wed, 7 Jan 2004 13:23:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266278AbUAGSXo (ORCPT ); Wed, 7 Jan 2004 13:23:44 -0500 Received: from mtaw4.prodigy.net ([64.164.98.52]:31625 "EHLO mtaw4.prodigy.net") by vger.kernel.org with ESMTP id S266333AbUAGSVJ (ORCPT ); Wed, 7 Jan 2004 13:21:09 -0500 Date: Wed, 7 Jan 2004 10:20:52 -0800 From: Mike Fedyk To: Jirka Kosina Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: XFS over 7.7TB LVM partition through NFS Message-ID: <20040107182052.GO1882@matchmail.com> Mail-Followup-To: Jirka Kosina , linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 23 On Wed, Jan 07, 2004 at 07:09:00PM +0100, Jirka Kosina wrote: > On Wed, 7 Jan 2004, Jirka Kosina wrote: > > > I am experiencing problems with LVM2 XFS partition in 2.6.0 being accessed > > over NFS. After exporting the filesystem clients start writing files to > > this partition over NFS, and after a short while we get this call trace, > > repeating indefinitely on the screen and the machine stops responding > > (keyboard, network): > > I am sorry, I have mis-pasted the log, it was not complete - there are two > extra lines before the Call Trace ... these two: > > Jan 8 01:38:35 storage2 kernel: 0x0: 94 38 73 54 cc 8c c9 be 0c 3e 6b 30 > 4c 9f 54 c5 > Jan 8 01:38:35 storage2 kernel: Filesystem "dm-0": XFS internal error > xfs_alloc_read_agf at line 2208 of file fs/xfs/xfs_alloc.c. Caller 0xc01fab06 Try a fsck on your xfs partitions. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/