public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Richard Weinberger <richard@nod.at>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	dedekind1@gmail.com, adrian.hunter@intel.com,
	linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: ubifs: noatime support?
Date: Thu, 18 Jan 2018 22:23:23 +0100	[thread overview]
Message-ID: <20180118212323.GA17412@amd> (raw)
In-Reply-To: <1996634.ggXeMYieCh@blindfold>

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

On Thu 2018-01-18 21:44:33, Richard Weinberger wrote:
> Pavel,
> 
> Am Donnerstag, 18. Januar 2018, 20:30:15 CET schrieb Pavel Machek:
> > Hi!
> > 
> > Ubifs seems to have atime support these days:
> > 
> >           sb->s_flags |= SB_ACTIVE;
> > #ifndef CONFIG_UBIFS_ATIME_SUPPORT
> >           sb->s_flags |= SB_NOATIME;
> > #else
> >           ubifs_msg(c, "full atime support is enabled.");
> > #endif
> > 
> > Which can be configured at compile-time, but no option to disable it
> > at runtime. What is going on there?
> > 
> > UBIFS: parse noatime
> > UBIFS error (ubi1:0 pid 94): ubifs_parse_options.constprop.5:
> > unrecognized mount option "noatime" e
> > mount: mounting ubi1:log_volume on /mnt/log failed: Invalid argument
> 
> Filesystems don't parse the "noatime" string, it is job of the mount tool to 
> translate it to the MS_NOATIME mount flag.

Ahha. I was using busybox version of mount. I guess I should check its
config. Thanks!
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2018-01-18 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 19:30 ubifs: noatime support? Pavel Machek
2018-01-18 20:44 ` Richard Weinberger
2018-01-18 21:23   ` Pavel Machek [this message]

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=20180118212323.GA17412@amd \
    --to=pavel@ucw.cz \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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