| To: | Ben Myers <bpm@xxxxxxx> |
|---|---|
| Subject: | Re: projid32bit=1 default in xfsprogs-3.2.0 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 14 Oct 2013 16:24:24 -0500 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20131014212347.GB1935@xxxxxxx> |
| References: | <525C1C15.7020204@xxxxxxxxxxx> <20131014211659.GI5663@dastard> <20131014212347.GB1935@xxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
On 10/14/13 4:23 PM, Ben Myers wrote: > 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 > Ok. Default it is! Thanks guys, just wanted to make sure we were all in agreement there. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: projid32bit=1 default in xfsprogs-3.2.0, Ben Myers |
|---|---|
| Next by Date: | Re: [PATCH] xfsprogs: fix resouce leak in longform_dir2_rebuild(), Dave Chinner |
| Previous by Thread: | Re: projid32bit=1 default in xfsprogs-3.2.0, Ben Myers |
| Next by Thread: | Re: projid32bit=1 default in xfsprogs-3.2.0, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |