Received: with ECARTIS (v1.0.0; list xfs); Tue, 22 Jan 2008 15:01:35 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.0-r574664 (2007-09-11) on oss.sgi.com X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=AWL,BAYES_50,RCVD_NUMERIC_HELO autolearn=no version=3.3.0-r574664 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m0MN1VAI014375 for ; Tue, 22 Jan 2008 15:01:32 -0800 X-ASG-Debug-ID: 1201042910-76b901e80000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from mail47.messagelabs.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with SMTP id 51EAD54B272 for ; Tue, 22 Jan 2008 15:01:50 -0800 (PST) Received: from mail47.messagelabs.com (mail47.messagelabs.com [216.82.240.163]) by cuda.sgi.com with SMTP id 1XNYhCpIdA0Ciw5Z for ; Tue, 22 Jan 2008 15:01:50 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: salmr0@bp.com X-Msg-Ref: server-14.tower-47.messagelabs.com!1201042906!37478421!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [129.230.248.73] Received: (qmail 7684 invoked from network); 22 Jan 2008 23:01:46 -0000 Received: from unknown (HELO bp1xeuav706.bp1.ad.bp.com) (129.230.248.73) by server-14.tower-47.messagelabs.com with SMTP; 22 Jan 2008 23:01:46 -0000 Received: from BP1XEUEX032.bp1.ad.bp.com ([149.184.176.166]) by bp1xeuav706.bp1.ad.bp.com with InterScan Messaging Security Suite; Tue, 22 Jan 2008 23:01:25 -0000 Received: from bp1xeuex007.bp1.ad.bp.com ([149.184.176.243]) by BP1XEUEX032.bp1.ad.bp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jan 2008 23:01:24 +0000 Received: from BP1XEUEX706-C.bp1.ad.bp.com ([149.182.218.110]) by bp1xeuex007.bp1.ad.bp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jan 2008 23:01:23 +0000 Received: from 149.179.228.36 ([149.179.228.36]) by BP1XEUEX706-C.bp1.ad.bp.com ([149.182.218.28]) with Microsoft Exchange Server HTTP-DAV ; Tue, 22 Jan 2008 23:01:22 +0000 Received: from holwrs01 by BP1XEUEX706-C.bp1.ad.bp.com; 22 Jan 2008 17:01:22 -0600 X-ASG-Orig-Subj: xfs_rapair memory requirement per TB Subject: xfs_rapair memory requirement per TB From: Rene Salmon To: xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 22 Jan 2008 17:01:22 -0600 Message-Id: <1201042882.32649.256.camel@holwrs01.bp.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 X-OriginalArrivalTime: 22 Jan 2008 23:01:23.0208 (UTC) FILETIME=[B5616080:01C85D4A] X-Barracuda-Connect: mail47.messagelabs.com[216.82.240.163] X-Barracuda-Start-Time: 1201042911 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -0.77 X-Barracuda-Spam-Status: No, SCORE=-0.77 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.0 tests=RCVD_NUMERIC_HELO, UNPARSEABLE_RELAY X-Barracuda-Spam-Report: Code version 3.1, rules version 3.1.40212 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 1.25 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO 0.00 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Virus-Scanned: ClamAV 0.91.2/5523/Tue Jan 22 11:31:19 2008 on oss.sgi.com X-Virus-Status: Clean X-archive-position: 14256 X-ecartis-version: Ecartis v1.0.0 Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com X-original-sender: salmr0@bp.com Precedence: bulk X-list: xfs Hi, Reading the "Repairing a possibly incomplete xfs_growfs command?" thread this month makes me wonder if there is some type of rough formula or guesstimation cheat sheet to figure out how much memory and swap one would need for an xfs_repair given a file system with many terabytes. Say I have an 8TB LUN that needs an xfs_repair. What would be the rough memory requirements and swap space? Thanks Rene