All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fleetwood <mike.fleetwood@googlemail.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [XFS SUMMIT] Deprecating V4 on-disk format
Date: Thu, 21 May 2020 09:29:43 +0100	[thread overview]
Message-ID: <CAMU1PDjKGBVqog+JRB9OmYXTsT4y_chnDTHbF9P8xCJxN=aXqA@mail.gmail.com> (raw)
In-Reply-To: <20200520151510.11837539@harpe.intellique.com>

On Wed, 20 May 2020 at 14:25, Emmanuel Florac <eflorac@intellique.com> wrote:
>
> Le Wed, 20 May 2020 11:14:30 +1000
> Dave Chinner <david@fromorbit.com> écrivait:
>
> > Well, there's a difference between what a distro that heavily
> > patches the upstream kernel is willing to support and what upstream
> > supports. And, realistically, v4 is going to be around for at least
> > one more major distro release, which means the distro support time
> > window is still going to be in the order of 15 years.
>
> IIRC, RedHat/CentOS v.7.x shipped with a v5-capable mkfs.xfs, but
> defaulted to v4. That means that unless you were extremely cautious
> (like I am :) 99% of RH/COs v7 will be running v4 volumes for the
> coming years. How many years, would you ask?

[Trying again hopefully without HTML]

So initial RHEL/CentOS 7 releases did create XFS v4 file systems.
However from RHEL/CentOS 7.3 [1] (circa Nov 2016) they are creating XFS
v5 file systems by default.


[1] RHEL 7.3 Release Notes > Chapter 9. File Systems
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.3_release_notes/new_features_file_systems


# cat /etc/centos-release
CentOS Linux release 7.8.2003 (Core)
# mkfs.xfs -V
mkfs.xfs version 4.5.0
# mkfs.xfs /dev/sdb13
...
# xfs_db -c version -r /dev/sdb13
versionnum [0xb4a5+0x18a] =
V5,NLINK,DIRV2,ALIGN,LOGV2,EXTFLG,MOREBITS,ATTR2,LAZYSBCOUNT,PROJID32BIT,CRC,FTYPE

  reply	other threads:[~2020-05-21  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  2:36 [XFS SUMMIT] Deprecating V4 on-disk format Dave Chinner
2020-05-19  6:23 ` Darrick J. Wong
2020-05-20  1:14   ` Dave Chinner
2020-05-20 13:15     ` Emmanuel Florac
2020-05-21  8:29       ` Mike Fleetwood [this message]
2020-05-26 17:16         ` Eric Sandeen
2020-05-25  3:23       ` Dave Chinner
2020-05-25  6:08         ` Darrick J. Wong
2020-05-25  7:02           ` Amir Goldstein
2020-05-25 10:01         ` Emmanuel Florac

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='CAMU1PDjKGBVqog+JRB9OmYXTsT4y_chnDTHbF9P8xCJxN=aXqA@mail.gmail.com' \
    --to=mike.fleetwood@googlemail.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=eflorac@intellique.com \
    --cc=linux-xfs@vger.kernel.org \
    /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.