From: keith.busch@intel.com (Keith Busch)
Subject: NVM and swap device
Date: Fri, 15 Jan 2016 21:19:01 +0000 [thread overview]
Message-ID: <20160115211901.GB14947@localhost.localdomain> (raw)
In-Reply-To: <20160115102052.0091a976@xeon-e3>
On Fri, Jan 15, 2016@10:20:52AM -0800, Stephen Hemminger wrote:
> Are these logs persistant?
Yep, these are persistent logs.
Nothing unusual here. Sorry for the digression.
> critical_warning : 0
> temperature : 29 C
> available_spare : 100%
> available_spare_threshold : 10%
> percentage_used : 0%
> data_units_read : 2,768,267
> data_units_written : 4,085,497
> host_read_commands : 74,458,451
> host_write_commands : 68,420,945
> controller_busy_time : 12
> power_cycles : 33
> power_on_hours : 227
> unsafe_shutdowns : 6
> media_errors : 0
> num_err_log_entries : 0
prev parent reply other threads:[~2016-01-15 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 3:40 NVM and swap device Stephen Hemminger
2016-01-13 8:26 ` Hannes Reinecke
2016-01-13 15:13 ` Matthew Wilcox
2016-01-13 17:47 ` Jens Axboe
2016-01-13 18:51 ` Stephen Hemminger
2016-01-13 18:55 ` Jens Axboe
2016-01-20 21:30 ` Stephen Hemminger
2016-01-15 17:42 ` Keith Busch
2016-01-15 18:18 ` Stephen Hemminger
2016-01-15 18:20 ` Stephen Hemminger
2016-01-15 21:19 ` Keith Busch [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=20160115211901.GB14947@localhost.localdomain \
--to=keith.busch@intel.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