linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Reichl <preichl@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH] xfsprogs: document attr2, ikeep option deprecation in xfs.5
Date: Tue,  2 Mar 2021 14:45:54 +0100	[thread overview]
Message-ID: <20210302134554.112408-1-preichl@redhat.com> (raw)

Since kernel v5.10, the (no)attr2 and (no)ikeep mount options are deprecated:

c23c393eaab5d xfs: remove deprecated mount options

Document this fact in the xfs(5) manpage.

Signed-off-by: Pavel Reichl <preichl@redhat.com>
---
 man/man5/xfs.5 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
index 7642662f..b657f0e4 100644
--- a/man/man5/xfs.5
+++ b/man/man5/xfs.5
@@ -118,6 +118,12 @@ to the file. Specifying a fixed allocsize value turns off
 the dynamic behavior.
 .TP
 .BR attr2 | noattr2
+Note: These options have been
+.B deprecated
+as of kernel v5.10; The noattr2 option will be removed no
+earlier than in September 2025 and attr2 option will be immutable
+default.
+.sp
 The options enable/disable an "opportunistic" improvement to
 be made in the way inline extended attributes are stored
 on-disk.  When the new form is used for the first time when
@@ -159,6 +165,13 @@ across the entire filesystem rather than just on directories
 configured to use it.
 .TP
 .BR ikeep | noikeep
+Note: These options have been
+.B deprecated
+as of kernel v5.10; The noikeep option will be removed no
+earlier than in September 2025 and ikeep option will be
+immutable default.
+
+.sp
 When ikeep is specified, XFS does not delete empty inode
 clusters and keeps them around on disk.  When noikeep is
 specified, empty inode clusters are returned to the free
-- 
2.29.2


             reply	other threads:[~2021-03-03  3:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 13:45 Pavel Reichl [this message]
2021-03-08 20:56 ` [PATCH] xfsprogs: document attr2, ikeep option deprecation in xfs.5 Eric Sandeen

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=20210302134554.112408-1-preichl@redhat.com \
    --to=preichl@redhat.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;
as well as URLs for NNTP newsgroup(s).