X-Spam-Checker-Version: SpamAssassin 3.3.0-rupdated (updated) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.0-rupdated Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id n4SCLYIJ253095 for ; Thu, 28 May 2009 07:21:35 -0500 X-ASG-Debug-ID: 1243513307-7248003e0000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from firestarter.dermichi.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id B54001D377BC for ; Thu, 28 May 2009 05:21:48 -0700 (PDT) Received: from firestarter.dermichi.com (firestarter.dermichi.com [83.64.48.195]) by cuda.sgi.com with ESMTP id to7BaKMchsqtrNJF for ; Thu, 28 May 2009 05:21:48 -0700 (PDT) Received: from cerberus.net4you.net ([194.177.153.130] helo=[192.168.200.110]) by firestarter.dermichi.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1M9ecF-0004Wv-92 for xfs@oss.sgi.com; Thu, 28 May 2009 14:21:47 +0200 Message-ID: <4A1E81D8.7010706@dermichi.com> Date: Thu, 28 May 2009 14:21:44 +0200 From: Michael Weissenbacher User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: xfs@oss.sgi.com X-ASG-Orig-Subj: regarding the inode64 mount option Subject: regarding the inode64 mount option Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Barracuda-Connect: firestarter.dermichi.com[83.64.48.195] X-Barracuda-Start-Time: 1243513308 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0074 1.0000 -1.9726 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -1.97 X-Barracuda-Spam-Status: No, SCORE=-1.97 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.26943 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on oss.sgi.com X-Virus-Status: Clean Hi XFS-List! I understand that the inode64 mount option allows inodes to be created beyond 1TB. There are also certain performance problems that can be cured by using this option when handling LOTS of inodes. During my tests i noticed that enabling it is like a one-way street. Inodes created with inode64 enabled aren't accessible when the option is left out. Now i got a few questions: - Does the inode64 option work only on 64bit architectures or is it also possible to use it with i686 - Is there a way to convert the inodes back - Why doesn't the filesystem remember that inode64 was used in the past and enable it automatically - Do i have to pass inode64 via grub / lilo if i want to use it on my root filesystem I haven't found any definitive clear documentation abount the pro's and con's, so maybe you can give me some hints :-) tia, Michael