All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: projid32bit=1 default in xfsprogs-3.2.0
Date: Mon, 14 Oct 2013 16:23:47 -0500	[thread overview]
Message-ID: <20131014212347.GB1935@sgi.com> (raw)
In-Reply-To: <20131014211659.GI5663@dastard>

On Tue, Oct 15, 2013 at 08:16:59AM +1100, Dave Chinner wrote:
> On Mon, Oct 14, 2013 at 11:30:13AM -0500, Eric Sandeen wrote:
> > The commit:
> > 
> > f3edb66a mkfs.xfs: validate options for CRCs up front.
> > 
> > unintentionally (?) defaulted to projid32bit=1 for all filesystems
> > at mkfs time.
> 
> It wasn't unintentional, I just forgot to document it.
> 
> > Support for 32 bit project IDs has been present since kernel v2.6.37.
> 
> Right, so taking the usual approach to these things, all the
> distro's now ship kernels that support 32 bit project IDs, so there
> is no reason for mkfs.xfs in a new xfsprogs release not to set it
> by default.

I'm not seeing much downside to turning on 32 bit project IDs by default in
3.2.0.  Sounds good to me.

-Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-10-14 21:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 16:30 projid32bit=1 default in xfsprogs-3.2.0 Eric Sandeen
2013-10-14 21:16 ` Dave Chinner
2013-10-14 21:23   ` Ben Myers [this message]
2013-10-14 21:24     ` Eric Sandeen
2013-10-15 19:46       ` Christoph Hellwig
2013-10-15 20:43         ` Christoph Hellwig
2013-10-15 21:22           ` Ben Myers
2013-10-15 21:31             ` Christoph Hellwig
2013-10-15 21:49               ` Ben Myers
2013-10-15 21:57                 ` Eric Sandeen
2013-10-15 22:48                   ` Dave Chinner
2013-10-15 22:59                     ` Eric Sandeen
2014-01-10 14:45           ` Rich Johnston
2014-01-11 10:30             ` Christoph Hellwig

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=20131014212347.GB1935@sgi.com \
    --to=bpm@sgi.com \
    --cc=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.