All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-ext4@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: Re: ext4 lazytime: ctime of some files changed
Date: Sat, 23 May 2015 15:24:15 +0200	[thread overview]
Message-ID: <55607F7F.1050106@web.de> (raw)
In-Reply-To: <555C4A65.5030100@web.de>

Jörg-Volker Peetz wrote on 05/20/2015 10:48:
<snip>
> after a few days of running the patch, I seem to have again two files with
> changed mtime without touching them (only reading by rsync).
> 
<snip>
I can affirm this error, but am not sure where to hunt.
I'm using several USB drives in a cycle for backup.
I have a directory with a file originally older than a few years.
Mount options are

$ grep sda /proc/mounts
/dev/sda2 /home ext4 rw,lazytime,relatime,nobarrier,errors=remount-ro 0 0

(using lazytime with relatime).
As reported, while I started using lazytime, this file's mtime got changed.
I reset the mtime with the "touch -r <intact_copy> <file>" command.
After a backup to one of the USB drives with something like

$ rsync -acv --exclude-from=<file> --delete-excluded <SRC> <DEST_ON_USB_DRIVE>

the namely file had its mtime changed  on the *source* device (the USB drive has
an ext4 fs mounted without the lazytime option).
I reset that again on the source SSD using "touch". Another file in the same was
also modified.

Next backup on another USB drive, same thing.
I took a look into the file list on the backup medium before the backup.
There the file also had a different mtime, but not the same mtime the file got
after the backup.

I'm confused.
Any idea?
-- 
Regards,
Jörg.


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-23 13:24 UTC|newest]

Thread overview: 16+ 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
2015-05-14 22:20   ` Theodore Ts'o
2015-05-15  7:17     ` Jörg-Volker Peetz
2015-05-15 15:14     ` Jörg-Volker Peetz
2015-05-15 23:11       ` Theodore Ts'o
2015-05-20  8:48         ` Jörg-Volker Peetz
2015-05-23 13:24           ` 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=55607F7F.1050106@web.de \
    --to=jvpeetz@web.de \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.