linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-fsdevel@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: ext4 lazytime: ctime of some files changed
Date: Wed, 13 May 2015 11:35:31 +0200	[thread overview]
Message-ID: <55531AE3.7030704@web.de> (raw)

Dear Ted,

on my laptop with ext4 fs (on SSD) I started to try the lazytime mount option
using a self compiled kernel 4.0.2 on a debian system with mount version 2.26.2.
Before that, I've used the noatime mount option.

After restarting the system with an adapted /etc/fstab file and the kernel
parameter "rootflags=lazytime", the relatime mount option was also set. I
changed that by commanding "mount -o remount,strictatime /", etc.
By accident, I noticed that some files had a modified ctime and mtime although
they were not changed or modified.

Has anybody else experienced that? Do I miss a patch?

Mount options in fstab: nobarrier,lazytime,errors=remount-ro
The filesystems are ext4 on a primary partition of the SSD with default mount
option journal_data_writeback. I created them in Feb 2011.

By the way, the command "mount -o remount,lazytime /" does not do the switch to
lazytime.

And thanks for your tireless work on Linux.
-- 
Regards,
jvp.


             reply	other threads:[~2015-05-13 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  9:35 Jörg-Volker Peetz [this message]
2015-05-13 16:20 ` ext4 lazytime: ctime of some files changed Jörg-Volker Peetz
2015-05-14  2:17 ` Theodore Ts'o
2015-05-14  8:27   ` Jörg-Volker Peetz
2015-05-14 12:38     ` Theodore Ts'o
2015-05-14 12:58       ` Jörg-Volker Peetz
2015-05-14 13:09         ` Jörg-Volker Peetz
2015-05-14 17:58         ` Jörg-Volker Peetz
2015-05-14  8:34   ` Jörg-Volker Peetz
2015-05-16 14:30 ` Holger Hoffstätte

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=55531AE3.7030704@web.de \
    --to=jvpeetz@web.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).