xfs
[Top] [All Lists]

Re: V5 format and man mkfs.xfs

To: Matthias Schniedermeyer <ms@xxxxxxx>
Subject: Re: V5 format and man mkfs.xfs
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 18 Jun 2014 08:46:58 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140617152917.GA17378@xxxxxxx>
References: <20140617082651.GA27971@xxxxxxx> <20140617123738.GH9508@dastard> <20140617152917.GA17378@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Jun 17, 2014 at 05:29:17PM +0200, Matthias Schniedermeyer wrote:
> On 17.06.2014 22:37, Dave Chinner wrote:
> > On Tue, Jun 17, 2014 at 10:26:51AM +0200, Matthias Schniedermeyer wrote:
> > > Hi
> > > 
> > > How seriously meant is "V5 isn't experimental anymore"?
> > 
> > "Fully supported" isn't a clear enough statement?
> 
> I guess that was a "selective memory"-bug on my side.
> 
> > > I ask because the man-page only mentions the syntax to enable it by 
> > > accident. A.k.a. the backport of ftype to V4.
> > > (man-page of xfsprogs 3.2.0 in Debian-SID)
> > 
> > That's intentional. V5 superblocks are an implementation detail that
> > most users don't even need to know about. They care about the name
> > of the features they are enabling at mkfs time, not the details of
> > the on-disk implementation of those features.
> 
> The question still stands.
> 
> The crc-option is only mentioned "by accident".
> Without the ftype backport there would be no mention of the "feature 
> crc".

Ok, so you're not reporting that we don't mention V5 filesystems as
"V5" filesystems. You're reporting that the "-m crc" option is not
documented. That's an oversight, and needs to be fixed.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>