From: tytso@mit.edu
To: Marcos Mello <marcosfrm@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Kernel does not respect tune2fs -E mount_opts=foo
Date: Tue, 23 Aug 2016 15:48:49 +0000 [thread overview]
Message-ID: <20160823154849.GA15892@thunk.org> (raw)
In-Reply-To: <CAJZVDJDeLePt1RYAtLQ-NzZ0R5nwRb_wwBW9H7dcgD2zG8_m=g@mail.gmail.com>
The problem you are running into is not something we can fix,
unfortunately, or at least not in a full and general way. The problem
is that there are certain mount options which are parsed by the mount
command (in userspace) and then translated to a mount flag, which is
then passed to the mount command as a bitmask, and which is
interpreted by the VFS layer before calling the file system.
The mount options field in the superblock is parsed by the ext4 file
system along with options that were not parsed by the mount binary,
passed to the VFS, which then passed it to ext4 file system driver.
In theory, we could interpret relatime in ext4 and replicate its
effects. For relatime, this is trivial to do. There may be other
mount options which are interepted by the mount userspace program, and
implemented in the VFS, where this would be much less easy to do.
> Other options like noacl, nouser_xattr, are ignored too. This
> filesystem is not listed in fstab.
This is exactly the same issue.
Cheers,
- Ted
next prev parent reply other threads:[~2016-08-23 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:57 Kernel does not respect tune2fs -E mount_opts=foo Marcos Mello
2016-08-23 15:48 ` tytso [this message]
2016-08-23 16:01 ` Marcos Mello
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=20160823154849.GA15892@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=marcosfrm@gmail.com \
/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