Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38019 - [arch-install-scripts] genfstab entry for f2fs partitions

Attached to Project: Arch Linux
Opened by Richard Jackson (richjn) - Thursday, 05 December 2013, 02:10 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 21 June 2014, 16:30 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I recently re-installed Arch to an ssd using the f2fs filesystem I created /etc/fstab via;

genfstab -p /mnt > /mnt/etc/fstab

which generated;

/dev/sda2 / f2fs rw,relatime,background_gc=on,user_xattr,acl,active_logs=6 0 0


On reboot I noticed dmesg contained an f2fs error for "unknown option user_xattr" and after removing the entry for user_xattr another entry for "unknown option acl" After a little background research it appears xattr and acl are both enabled by default in the Arch offical kernel config and that the options (if you wished to change that behaviour) would be "nouser_xattr" and "noacl" to turn them off.

Not sure if this is an actual issue or just "noise", which if it is my apologies, but thought I should report it.


Additional info:
Arch ISO December 2013
arch-install-scripts-12-1


Steps to reproduce:
Install Arch from offical install ISO and generate /etc/fstab with genfstab
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 21 June 2014, 16:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  https://projects.archlinux.org/arch-inst all-scripts.git/commit/?id=03121cb504c4
Comment by Dave Reisner (falconindy) - Thursday, 05 December 2013, 02:21 GMT
It's a kernel bug if the filesystem displays options that it doesn't understand. This is done on a per-filesystem basis. There's no such thing as global defaults for ACLs and xattrs since the implementation is reliant on the code from the backing filesystem.
Comment by Dave Reisner (falconindy) - Thursday, 05 December 2013, 02:25 GMT
FWIW, this wouldn't be the first case...

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c6c20372bbb2f70d2757eed0a8d6860884bae11f
Comment by Richard Jackson (richjn) - Thursday, 05 December 2013, 04:44 GMT
I think the issue may be that genfstab is generating non-existent mount options for fstab but having said that I confess to having no knowledge of how genfstab works or any knowledge of f2fs

This is the reference I looked up (see the mount options at bottom of page)
http://praxis.edoceo.com/kernel/doc/filesystems/f2fs.txt

Comment by Dave Reisner (falconindy) - Thursday, 05 December 2013, 15:05 GMT
> I confess to having no knowledge of how genfstab works or any knowledge of f2fs
genfstab reads (indirectly) /proc/self/mountinfo to get the current mount options. This isn't something I'm just making up. The kernel reports it as an enabled option, so genfstab reuses it. f2fs should be allowing "user_xattr" and "acl" as NOOP options. There's plenty of precedent for this if you look at other FS's like ext4...

I'd rather not get into the game of applying quirks for tons of filesystems. More to the point, genfstab was never meant to be a 100% solution (thanks to crap like this).

This really should be fixed in the kernel.
Comment by Richard Jackson (richjn) - Thursday, 05 December 2013, 16:22 GMT
> I'd rather not get into the game of applying quirks for tons of filesystems
I can understand that.

Thanks for taking the time to explain, I have opened an upstream bug report.
https://bugzilla.kernel.org/show_bug.cgi?id=66631

Loading...