https://bugzilla.kernel.org/show_bug.cgi?id=211605 --- Comment #2 from Dave Chinner (david@xxxxxxxxxxxxx) --- On Sun, Feb 07, 2021 at 05:06:36AM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxx > Reporter: cuihao.leo@xxxxxxxxx > 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. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
