From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 oBE4g82k069194 for ; Mon, 13 Dec 2010 22:42:08 -0600 Received: from mail.internode.on.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 4BB3D1CC0DF6 for ; Mon, 13 Dec 2010 20:43:58 -0800 (PST) Received: from mail.internode.on.net (bld-mail15.adl6.internode.on.net [150.101.137.100]) by cuda.sgi.com with ESMTP id qdrixxL0E26J8DBR for ; Mon, 13 Dec 2010 20:43:58 -0800 (PST) Date: Tue, 14 Dec 2010 15:43:55 +1100 From: Dave Chinner Subject: Re: inode64 mount option added after data exists Message-ID: <20101214044355.GB16267@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: Ivan.Novick@emc.com Cc: xfs@oss.sgi.com On Mon, Dec 13, 2010 at 05:24:46PM -0500, Ivan.Novick@emc.com wrote: > Hi all, > > Quick question about the inode64 mount option. > > Is it safe to add this mount option to a file system that was > already created and wrote lots of data without it. Yes. > Will it still work as intended in this case (use 64 bit inodes)? Yes, for newly created inodes and data. Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs