From: "Ted Ts'o" <tytso@mit.edu>
To: Neil Clarkson <neilaclarkson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext4 bug? last write time precedes last mount time on a writable volume!
Date: Fri, 2 Mar 2012 15:45:21 -0500 [thread overview]
Message-ID: <20120302204521.GD22215@thunk.org> (raw)
In-Reply-To: <CADzG2TC8y=sYVYx0rVLAo_o6Mo2tjMOJYAw97ZhKAmNX555a6w@mail.gmail.com>
On Fri, Mar 02, 2012 at 12:39:57PM +0000, Neil Clarkson wrote:
> Isn't the s_wtime field of the ext4 superblock supposed to show the
> time, in seconds since the epoch, of the last write? It isn't
> happening!
It shows the last time the superblock has been modified, and one of
the things that we've been doing lately has been to optimize ext4 so
that it writes to the superblock *much* less often. It was a
performance bottleneck to be constantly updating the number of free
blocks in the superblock each time we write to a new block, for
example --- or update the superblock to update the number of free
inodes each time we allocate a new inode.
Is there a reason why you particularly care about s_wtime being
updated?
- Ted
next prev parent reply other threads:[~2012-03-02 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:39 ext4 bug? last write time precedes last mount time on a writable volume! Neil Clarkson
2012-03-02 20:45 ` Ted Ts'o [this message]
2012-03-02 21:35 ` Neil Clarkson
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=20120302204521.GD22215@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=neilaclarkson@gmail.com \
/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