From: Andi Kleen <andi@firstfloor.org>
To: Neil Clarkson <neilaclarkson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext4 superblock last write time clearly isnt the last write time
Date: Thu, 23 Feb 2012 14:01:24 -0800 [thread overview]
Message-ID: <m2r4xlp5u3.fsf@firstfloor.org> (raw)
In-Reply-To: <CADzG2TCx8OtpBqwEA1VNN-PUFcPU5WBns2D5LtsZZu9mXUgeOQ@mail.gmail.com> (Neil Clarkson's message of "Thu, 23 Feb 2012 21:27:50 +0000")
Neil Clarkson <neilaclarkson@gmail.com> writes:
> Isn't the s_wtime field of the ext4 superblock supposed to show the
> time, in seconds since the epoch, of the last write to the file
> system?
Last write to the super block. Obviously last write to the file system
would be incredible expensive: every write to the file system would
cause a super block write too, doubling all write IO.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-02-23 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 21:27 ext4 superblock last write time clearly isnt the last write time Neil Clarkson
2012-02-23 22:01 ` Andi Kleen [this message]
2012-02-24 8:19 ` 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=m2r4xlp5u3.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--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