linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: funky.shelf@gmail.com
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: EXT4 Statistics
Date: Tue, 29 Dec 2015 10:23:01 -0500	[thread overview]
Message-ID: <20151229152301.GD3248@thunk.org> (raw)
In-Reply-To: <5681b67a.44de8c0a.82c37.3f52@mx.google.com>

On Mon, Dec 28, 2015 at 02:23:54PM -0800, funky.shelf@gmail.com wrote:
> Would it be possible to store the number of successful read and
> write operations that a regular file witnesses during its lifetime?
> I'm sorry if this question has been asked before. If the information
> is already available, where may one find it?

Ext4 doesn't currently do this; if it did it would be a performance
disaster, so it's not likely that it's something we would add.

Why would you want such a thing?  What are you trying to do?

						- Ted

      reply	other threads:[~2015-12-29 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 22:23 EXT4 Statistics funky.shelf
2015-12-29 15:23 ` Theodore Ts'o [this message]

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=20151229152301.GD3248@thunk.org \
    --to=tytso@mit.edu \
    --cc=funky.shelf@gmail.com \
    --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).