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: Tue, 17 Jun 2014 22:37:38 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20140617082651.GA27971@xxxxxxx>
References: <20140617082651.GA27971@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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 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.

> And you still have to know that crc means V5.

Why do you care about the format mkfs.xfs chooses for you - it's
based on the features you requested. V5 isn't magically faster than
V4 - there are many cases where it is slower due to CRC overhead
or the overhead of the larger inode it requires. So unless you
request a feature that requires it at mkfs time, you don't get that
format.

In a year or so we'll change the mkfs default so that CRCs are
enabled by default, but we can't do that until all the distro's have
had time to pick up a kernel that fully supports the CRC feature....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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