Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 01:25:06 -0700 (PDT) Received: from amanpulo.hosting.qsr.com.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7B8P1H9031329 for ; Thu, 11 Aug 2005 01:25:01 -0700 Received: from localhost (localhost [127.0.0.1]) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 94F8A1C519BF for ; Thu, 11 Aug 2005 16:22:47 +0800 (PHT) Received: from musang.free.net.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 3291E1C5198C for ; Thu, 11 Aug 2005 16:22:43 +0800 (PHT) Received: by musang.free.net.ph (Postfix, from userid 1000) id 17E5616AFA7FA; Thu, 11 Aug 2005 16:22:41 +0800 (PHT) Date: Thu, 11 Aug 2005 16:22:41 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: XFS repair problem Message-ID: <20050811082241.GJ2779@free.net.ph> Mail-Followup-To: linux-xfs@oss.sgi.com References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost> <20050809120823.E13484145@melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050809120823.E13484145@melbourne.sgi.com> X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.9i X-archive-position: 5784 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1530 Lines: 40 On Tue, Aug 09, 2005 at 12:08:23PM +1000, David Chinner wrote: > Swap won't help if you're running an ia32 (32bit) kernel - you have a > per-process memory limit of 1-4GiB (depending on kernel and config). > The amount of physical memory and swap does not change this > limitation. I have an ia32 box running Debian Sarge (xfsprogs 2.6.20) with Linux 2.6.12.4, 3GB physical memory, and at present 2GB swap. We don't have a 64-bit system with more RAM to which we can transfer our filesystems, if ever, so I'd like to know: 1. What kernel configuration do we need to enable in particular to maximize the per-process memory limit? 2. What limit should I follow for per-filesystem size, so that I can be confident that even when the filesystem has reasonably many inodes both xfs_check and xfs_repair will work without hitting the per-process memory limit of Linux on ia32? Also, I am using LVM2 (2.01.04) to allow me to build my XFS filesystems across multiple physical volumes (each physical volume is an external hardware RAID 5 enclosure connected to the system via SCSI). I wonder: 1. Are there any known issues with XFS and LVM2 when the total volume group size gets very big (eg: >2TiB)? Or does XFS not care and will this be a purely LVM issue? 2. Aside from problems with snapshots, are there any known issues with running XFS on top of LVM2? Cheers! --> Jijo -- Federico Sevilla III : jijo.free.net.ph : When we speak of free software GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price.