Received: with ECARTIS (v1.0.0; list xfs); Tue, 11 Dec 2007 14:16:05 -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.7 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_43 autolearn=no version=3.3.0-r574664 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with SMTP id lBBMFtvx002837 for ; Tue, 11 Dec 2007 14:16:00 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA12780; Wed, 12 Dec 2007 09:16:00 +1100 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id lBBMFxIN5471993; Wed, 12 Dec 2007 09:15:59 +1100 (AEDT) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id lBBMFtOd5470770; Wed, 12 Dec 2007 09:15:55 +1100 (AEDT) X-Authentication-Warning: snort.melbourne.sgi.com: dgc set sender to dgc@sgi.com using -f Date: Wed, 12 Dec 2007 09:15:55 +1100 From: David Chinner To: David Sparks Cc: xfs@oss.sgi.com Subject: Re: mkfs.xfs ... lazy-count=1 ... not mountable by older kernels? Message-ID: <20071211221554.GC4612@sgi.com> References: <475EE83A.3060607@ca.sophos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <475EE83A.3060607@ca.sophos.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.91.2/5093/Tue Dec 11 10:00:45 2007 on oss.sgi.com X-Virus-Status: Clean X-archive-position: 13907 X-ecartis-version: Ecartis v1.0.0 Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: xfs On Tue, Dec 11, 2007 at 11:42:50AM -0800, David Sparks wrote: > Hi all, > > Is it expected that filesystems made with lazy-count=1 are not mountable by > older kernels? That is expected. lazy-count is a mkfs option because it changes the on-disk format slightly, and older kernels do not understand that format. Hence mkfs sets a superblock feature bit to prevent the filesystem from being mounted on kernels that don't understand the slightly different disk format. Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group