public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: rfc: kill ino64 mount option
Date: Sat, 28 Jun 2008 17:23:03 +0200	[thread overview]
Message-ID: <20080628152303.GA22484@lst.de> (raw)
In-Reply-To: <20080628000914.GE29319@disturbed>

On Sat, Jun 28, 2008 at 10:09:14AM +1000, Dave Chinner wrote:
> On Fri, Jun 27, 2008 at 05:39:28PM +0200, Christoph Hellwig wrote:
> > Does anyone have objections to kill the ino64 mount option?  It's purely
> > a debug tool to force inode numbers outside of the range representable
> > in 32bits and is quite invasive for something that could easily be
> > debugged by just having a large enough filesystem..
> 
> It's the "large enough fs" that is the problem. XFSQA uses
> small partitions for the most part, and this allows testing
> of 64 bit inode numbers with a standard qa config.

Well, it allows showing 64bit inode numbers to userspace.  All XFS
internal codepathes are still using the smaller inode numbers and we
only add a fixed offset to them just before the inode number is returned
to userspace.

  parent reply	other threads:[~2008-06-28 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 15:39 rfc: kill ino64 mount option Christoph Hellwig
2008-06-28  0:09 ` Dave Chinner
2008-06-28  0:46   ` Mark Goodwin
2008-06-28  4:31     ` Eric Sandeen
2008-06-28 15:25       ` Christoph Hellwig
2008-06-28 19:52         ` Eric Sandeen
2008-07-01  8:07     ` Christoph Litauer
2008-07-01 14:12       ` Mark Goodwin
2008-07-01 14:45         ` Christoph Litauer
2008-06-28 15:23   ` Christoph Hellwig [this message]
2008-06-29 23:13     ` Nathan Scott

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=20080628152303.GA22484@lst.de \
    --to=hch@lst.de \
    --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