From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-fsdevel@vger.kernel.org
Subject: Re: ext4 lazytime: ctime of some files changed
Date: Wed, 13 May 2015 18:20:35 +0200 [thread overview]
Message-ID: <mivtkj$fhi$1@ger.gmane.org> (raw)
In-Reply-To: <55531AE3.7030704@web.de>
Jörg-Volker Peetz wrote on 05/13/2015 11:35:
> 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.
>
After writing the above, I encountered another accident regarding two files of
the emacs24 package of which the mtime got changed.
I tried to repair this by using versions of the two files with the correct mtime
in the /tmp directory and commanded
> touch -r /tmp/debian-ispell.elc
/usr/share/emacs24/site-lisp/dictionaries-common/debian-ispell.elc
> touch -r /tmp/ess-noweb-font-lock-mode.elc
/usr/share/emacs24/site-lisp/ess/ess-noweb-font-lock-mode.elc
A few hours later I unpacked and tested a tar archive by commanding s.t. like
> tar xf linux-4.0.tar.xz
> sync
> echo 3 >/proc/sys/vm/drop_caches
> tar df linux-4.0.tar.xz
Thereafter, the two emacs package files again had a wrong mtime (which by the
way shows when I start emacs).
Could this be due to the lazytime mount option?
--
Regards,
jvp.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-13 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 9:35 ext4 lazytime: ctime of some files changed Jörg-Volker Peetz
2015-05-13 16:20 ` Jörg-Volker Peetz [this message]
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='mivtkj$fhi$1@ger.gmane.org' \
--to=jvpeetz@web.de \
--cc=linux-fsdevel@vger.kernel.org \
/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).