diff mbox

xfsprogs: Remove barrier/nobarrier mount options from xfs.5

Message ID 7105a6a3-bd16-53be-2e4f-d1ec8a491d20@sandeen.net (mailing list archive)
State Accepted, archived
Headers show

Commit Message

Eric Sandeen June 26, 2018, 12:06 a.m. UTC
Remove the now-removed barrier/nobarrier mount options from
the xfs.5 manpage.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---


--
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

Comments

Carlos Maiolino June 26, 2018, 11:20 a.m. UTC | #1
On Mon, Jun 25, 2018 at 07:06:51PM -0500, Eric Sandeen wrote:
> Remove the now-removed barrier/nobarrier mount options from
> the xfs.5 manpage.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Although the option is scheduled to be removed in 4.19, I think it's worth to
remove it from xfsprogs before the mount option removal patch lands in kernel,
so:

Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>


> ---
> 
> diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
> index 745dad4..628bfc3 100644
> --- a/man/man5/xfs.5
> +++ b/man/man5/xfs.5
> @@ -132,20 +132,6 @@ by the filesystem.
>  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
> -devices that support write barriers.
> -.sp
> -Barriers are enabled by default.
> -.TP
>  .BR discard | nodiscard
>  Enable/disable the issuing of commands to let the block
>  device reclaim space freed by the filesystem.  This is
> 
> --
> 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
diff mbox

Patch

diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
index 745dad4..628bfc3 100644
--- a/man/man5/xfs.5
+++ b/man/man5/xfs.5
@@ -132,20 +132,6 @@  by the filesystem.
 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
-devices that support write barriers.
-.sp
-Barriers are enabled by default.
-.TP
 .BR discard | nodiscard
 Enable/disable the issuing of commands to let the block
 device reclaim space freed by the filesystem.  This is