From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH] xfsprogs: document barrier deprecation in xfs(5)
Date: Mon, 10 Apr 2017 11:53:53 -0500 [thread overview]
Message-ID: <d24e1def-2f2d-5699-46e0-633d613004da@redhat.com> (raw)
Since kernel v4.10, the barrier mount option is deprecated:
2291dab2 xfs: Always flush caches when integrity is required
4cf4573d xfs: deprecate barrier/nobarrier mount option
Document this fact in the xfs(5) manpage.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
index c7fb780..745dad4 100644
--- a/man/man5/xfs.5
+++ b/man/man5/xfs.5
@@ -133,6 +133,12 @@ CRC enabled filesystems always use the attr2 format, and so
will reject the noattr2 mount option if it is set.
.TP
.BR barrier | nobarrier
+Note: This option has been
+.B deprecated
+as of kernel v4.10; in that version, integrity operations are
+always performed and the mount option is ignored. These mount
+options will be removed no earlier than kernel v4.15.
+.sp
Enables/disables the use of block layer write barriers for
writes into the journal and for data integrity operations.
This allows for drive level write caching to be enabled, for
next reply other threads:[~2017-04-10 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 16:53 Eric Sandeen [this message]
2017-04-10 22:38 ` [PATCH] xfsprogs: document barrier deprecation in xfs(5) Darrick J. Wong
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=d24e1def-2f2d-5699-46e0-633d613004da@redhat.com \
--to=sandeen@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 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.