From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 48751] ext3: ctime changes with no reason in 30 seconds after a file change
Date: Wed, 17 Oct 2012 22:52:55 +0000 (UTC) [thread overview]
Message-ID: <20121017225255.A0D6411FC3E@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-48751-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=48751
Jan Kara <jack@suse.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jack@suse.cz
--- Comment #4 from Jan Kara <jack@suse.cz> 2012-10-17 22:52:55 ---
Yeah, the reason is that /tmp/a/usr/lib/locale/locale-archive is written to via
mmap. ext3 (since it does not support delayed allocation) allocates blocks for
the written data only when flusher thread decides to do writeback on the inode
(which is 30s after the file is written). This allocation changes i_blocks
field of the inode and thus inode's ctime has to be changed as well.
I understand this is counter-intuitive but that's just how the filesystem
works...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-10-17 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 18:07 [Bug 48751] New: ext3: ctime changes with no reason in 30 seconds after a file change bugzilla-daemon
2012-10-13 18:11 ` [Bug 48751] " bugzilla-daemon
2012-10-13 18:14 ` bugzilla-daemon
2012-10-14 12:28 ` bugzilla-daemon
2012-10-15 17:41 ` bugzilla-daemon
2012-10-17 22:52 ` bugzilla-daemon [this message]
2012-10-17 22:53 ` bugzilla-daemon
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=20121017225255.A0D6411FC3E@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).