linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nebojsa Trpkovic <trx.lists@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: lifetime_write_kbytes isn't preserved during unclean shutdown
Date: Sun, 27 Jun 2010 18:56:07 +0200	[thread overview]
Message-ID: <4C2782A7.7040301@gmail.com> (raw)

I've noticed that lifetime_write_kbytes isn't preserved during unclean
shutdown.
At least on my Intel X25-V, but I guess it's ext4's issue, not Intel's
one. :)

lifetime_write_kbytes constantly grow while using filesystem. If
computer is rebooted regulary with clean unmount, next time it boots
lifetime_write_kbytes will continue incrementing counter and everything
seems to work right.

Then again, if there was unclean shutdown/reboot, lifetime_write_kbytes
will be reset to value of last clean unmount. Example:

lifetime_write_kbytes 18 GB
lifetime_write_kbytes 20 GB
lifetime_write_kbytes 22 GB
clean reboot
lifetime_write_kbytes 22 GB
lifetime_write_kbytes 24 GB
lifetime_write_kbytes 26 GB
unclean reboot (reboot switch/power failure/whatever)
lifetime_write_kbytes 22 GB
...

I guess that /sys takes value written in filesystem itself and increment
it during system operation, but writes back new lifetime_write_kbytes
value to filesystem just on clean unmount.
It seems it would not hurt to write periodicly, maybe not too often - 10
minutes or so, intermidiate lifetime_write_kbytes value to filesystem
and avoid unnecessary lost of lifetime_writes on unclean reboot.

Nebojsa Trpkovic


             reply	other threads:[~2010-06-27 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 16:56 Nebojsa Trpkovic [this message]
2010-06-28 19:57 ` lifetime_write_kbytes isn't preserved during unclean shutdown tytso
2010-06-30  5:46   ` Andreas Dilger
2010-06-30 13:31     ` tytso
2010-06-30 21:54       ` Andreas Dilger

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=4C2782A7.7040301@gmail.com \
    --to=trx.lists@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).