From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 211605] New: Re-mount XFS causes "noattr2 mount option is deprecated" warning
Date: Sun, 07 Feb 2021 05:06:36 +0000 [thread overview]
Message-ID: <bug-211605-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=211605
Bug ID: 211605
Summary: Re-mount XFS causes "noattr2 mount option is
deprecated" warning
Product: File System
Version: 2.5
Kernel Version: 5.10.13
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: cuihao.leo@gmail.com
Regression: No
Created attachment 295103
--> https://bugzilla.kernel.org/attachment.cgi?id=295103&action=edit
proposed fix
After recent kernel update, I notice "XFS: noattr2 mount option is deprecated."
kernel message every time I shutdown the system. It turns out that remounting a
XFS causes the warning.
Steps to Reproduce:
1) Mount a XFS and remount it with different options:
> $ mount some_xfs.img /mnt/test
> $ mount -o remount,ro /mnt/test
2) Check kernel message. Remounting causes a line of warning:
> XFS: noattr2 mount option is deprecated.
I had checked my fstab and kernel params and didn't found any use of "attr2"
option. It doesn't break things, but is a little confusing.
Build Information:
Arch Linux stock kernel.
Linux cvhc-tomato 5.10.13-arch1-1 #1 SMP PREEMPT Wed, 03 Feb 2021 23:44:07
+0000 x86_64 GNU/Linux
Additional Information:
The warning is introduced in commit c23c393e. I guess remounting triggers it
because XFS driver still writes attr2 option to /proc/mounts:
> $ grep attr2 /proc/mounts
> /dev/nvme0n1p3 / xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota
> 0 0
"attr2" is default so it should be omitted in mount options. A potential fix
(attached, untested) is to hide it and make "noattr2" explicit in
xfs_fs_show_options.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-02-07 5:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 5:06 bugzilla-daemon [this message]
2021-02-07 22:15 ` [Bug 211605] New: Re-mount XFS causes "noattr2 mount option is deprecated" warning Dave Chinner
2021-02-07 22:53 ` Eric Sandeen
2021-02-07 23:18 ` Dave Chinner
2021-02-07 23:36 ` Eric Sandeen
2021-02-07 22:41 ` [Bug 211605] " bugzilla-daemon
2021-02-07 22:42 ` bugzilla-daemon
2021-02-07 22:56 ` bugzilla-daemon
2021-02-07 23:01 ` bugzilla-daemon
2021-02-07 23:06 ` bugzilla-daemon
2021-02-07 23:18 ` [Bug 211605] Re-mount XFS causes "attr2 " bugzilla-daemon
2021-02-07 23:36 ` bugzilla-daemon
2021-03-08 7:04 ` bugzilla-daemon
2021-03-08 15:07 ` bugzilla-daemon
2021-05-03 13:31 ` bugzilla-daemon
2021-05-03 13:35 ` bugzilla-daemon
2021-05-13 11:15 ` bugzilla-daemon
2021-05-13 13:22 ` bugzilla-daemon
2025-11-15 8:12 ` bugzilla-daemon
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=bug-211605-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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.