From: Emmanuel Florac <eflorac@intellique.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>, linux-xfs@vger.kernel.org
Subject: Re: [XFS SUMMIT] Deprecating V4 on-disk format
Date: Wed, 20 May 2020 15:15:10 +0200 [thread overview]
Message-ID: <20200520151510.11837539@harpe.intellique.com> (raw)
In-Reply-To: <20200520011430.GS2040@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
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?
As for the lifecycle of a filesystem, I just ended support on a 40 TB
archival server I set up back in 2007. I still have a number of
supported systems from the years 2008-2010, and about a hundred from
2010-2013. That's how reliable XFS is, unfortunately :)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2020-05-20 13:25 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 [this message]
2020-05-21 8:29 ` Mike Fleetwood
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=20200520151510.11837539@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox