public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: David Sparks <dave@ca.sophos.com>
Cc: xfs@oss.sgi.com
Subject: Re: mkfs.xfs ... lazy-count=1 ... not mountable by older kernels?
Date: Wed, 12 Dec 2007 09:15:55 +1100	[thread overview]
Message-ID: <20071211221554.GC4612@sgi.com> (raw)
In-Reply-To: <475EE83A.3060607@ca.sophos.com>

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

  reply	other threads:[~2007-12-11 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 19:42 mkfs.xfs ... lazy-count=1 ... not mountable by older kernels? David Sparks
2007-12-11 22:15 ` David Chinner [this message]
2007-12-12  0:37   ` Timothy Shimmin
2007-12-12 13:19     ` Justin Piszcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071211221554.GC4612@sgi.com \
    --to=dgc@sgi.com \
    --cc=dave@ca.sophos.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox