From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfsprogs: document barrier deprecation in xfs(5)
Date: Mon, 10 Apr 2017 15:38:55 -0700 [thread overview]
Message-ID: <20170410223855.GH10459@birch.djwong.org> (raw)
In-Reply-To: <d24e1def-2f2d-5699-46e0-633d613004da@redhat.com>
On Mon, Apr 10, 2017 at 11:53:53AM -0500, Eric Sandeen wrote:
> 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>
Looks ok.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
>
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-04-10 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 16:53 [PATCH] xfsprogs: document barrier deprecation in xfs(5) Eric Sandeen
2017-04-10 22:38 ` Darrick J. Wong [this message]
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=20170410223855.GH10459@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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.