XFS (dm-4): unknown mount option [nobarrier]

现象：业务将CentOS 7系统升级到4.19内核，发现分区/dev/VolGroup00/Data 无法挂载，报错如下

# cat /root/OSInfo
CentOS7.2 auto

# uname -r
4.19.61-300.el7.x86_64

# dmesg |tail
[ 994.342353] XFS (dm-4): unknown mount option [nobarrier].
[ 1018.174020] XFS (dm-4): unknown mount option [nobarrier].
[ 1051.207481] XFS (dm-4): unknown mount option [nobarrier].
[ 1107.472248] XFS (dm-4): unknown mount option [nobarrier].
[ 1971.262372] XFS (dm-4): unknown mount option [nobarrier].
[ 2649.732824] XFS (dm-4): unknown mount option [nobarrier].
[ 2675.778700] XFS (dm-4): unknown mount option [nobarrier].
[ 4727.187483] XFS (dm-4): unknown mount option [nobarrier].
[ 4923.508659] XFS (dm-4): Mounting V5 Filesystem
[ 4923.558194] XFS (dm-4): Ending clean mount

根据参考文档 https://patchwork.kernel.org/patch/10487561/ ，应该是高版本内核4.15之后，取消了两个相关参数（barrier/nobarrier），将其去掉后挂载正常了。

cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Sat May 9 14:33:44 2020
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/VolGroup00-LogVol03 / xfs defaults 0 0
UUID=b613175e-29d0-425d-9be3-5d41624e7f45 /boot xfs defaults 0 0
/dev/mapper/VolGroup00-LogVol01 /tmp xfs defaults 0 0
/dev/mapper/VolGroup00-LogVol02 /var xfs defaults 0 0
/dev/mapper/VolGroup00-LogVol00 swap swap defaults 0 0
/dev/VolGroup00/Data /data xfs defaults,noatime 0 0

 

 

The barrier mount options have been no-ops and deprecated since

4cf4573 xfs: deprecate barrier/nobarrier mount option

i.e. kernel 4.10 / December 2016, with a stated deprecation schedule
after v4.15.  Should be fair game to remove them now.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
 Documentation/filesystems/xfs.txt |    4 ++--
 fs/xfs/xfs_mount.h                |    1 -
 fs/xfs/xfs_super.c                |   34 ++++------------------------------
 3 files changed, 6 insertions(+), 33 deletions(-)



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