From: Dave Chinner <david@fromorbit.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [Bug 211605] New: Re-mount XFS causes "noattr2 mount option is deprecated" warning
Date: Mon, 8 Feb 2021 09:15:05 +1100 [thread overview]
Message-ID: <20210207221505.GW4662@dread.disaster.area> (raw)
In-Reply-To: <bug-211605-201763@https.bugzilla.kernel.org/>
On Sun, Feb 07, 2021 at 05:06:36AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> 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.
That sounds like a mount(1) bug, not a kernel bug. Something is
adding the "noattr2" option to the remount line. Running you test
on my system doesn't show that warning. I'm running a 5.11-rc5 kernel
and:
$ mount -V
mount from util-linux 2.36 (libmount 2.36.0: selinux, smack, btrfs, namespaces, assert, debug)
$
And there is no such "noattr2 is deprecated" output. What version of
mount are you running?
What we really need from your system is debug that tells us exactly
what the mount option string that the mount command is handing the
mount syscall.
> 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.
"attr2" != "noattr2"
The kernel is warning about a mount option being specified that
isn't even in the set emitted in /proc/mounts. Nor is it on your
command line. Yet the kernel is warning about it, and that implies
that mount has passed it to the kernel incorrectly.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-02-07 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 5:06 [Bug 211605] New: Re-mount XFS causes "noattr2 mount option is deprecated" warning bugzilla-daemon
2021-02-07 22:15 ` Dave Chinner [this message]
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=20210207221505.GW4662@dread.disaster.area \
--to=david@fromorbit.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox