From: stephen@networkplumber.org (Stephen Hemminger)
Subject: NVM and swap device
Date: Fri, 15 Jan 2016 10:18:19 -0800 [thread overview]
Message-ID: <20160115101819.2e63b19b@xeon-e3> (raw)
In-Reply-To: <20160115174236.GC11165@localhost.localdomain>
On Fri, 15 Jan 2016 17:42:36 +0000
Keith Busch <keith.busch@intel.com> wrote:
> On Tue, Jan 12, 2016@07:40:30PM -0800, Stephen Hemminger wrote:
> > I have a nice shiny new Intel NVM PCI card; decided to use it for a filesystem and swap.
> > The filesystem (btrfs) is doing fine, but the swap device was throwing occasional
> > random errors. Suspect a driver problem rather than hardware.
> >
> > I am using 4.4 kernel without patches.
> >
> > kern.log:Jan 12 08:11:57 xeon-e3 kernel: [159474.037390] Read-error on swap-device (259:0:17597808)
> > kern.log.1:Jan 7 08:32:10 xeon-e3 kernel: [87938.855526] Read-error on swap-device (259:0:11355648)
> > kern.log.1:Jan 7 08:32:10 xeon-e3 kernel: [87938.855530] Read-error on swap-device (259:0:11355656)
> > kern.log.1:Jan 7 08:32:10 xeon-e3 kernel: [87939.855467] Read-error on swap-device (259:0:16180824)
> > kern.log.1:Jan 8 08:24:07 xeon-e3 kernel: [63670.777981] Read-error on swap-device (259:0:32690768)
> > kern.log.1:Jan 9 09:25:02 xeon-e3 kernel: [153720.919325] Read-error on swap-device (259:0:220488)
> > kern.log.1:Jan 9 16:40:05 xeon-e3 kernel: [179820.957675] Read-error on swap-device (259:0:24476232)
> > kern.log.1:Jan 9 16:40:05 xeon-e3 kernel: [179820.962673] Read-error on swap-device (259:0:33292816)
> >
> > The swap device was being added via /etc/fstab by UUID.
>
> If you haven't any further insights into the issue, could you check the
> device's health? I'd be surprised if there is a problem with that since
> you mentioned it was new card, but would like to rule that out if this
> has hit a dead end on the other testing.
>
> For that, we need smart logs. There are various tools available that
> can read those logs. Here's an open source version:
>
> https://github.com/linux-nvme/nvme-cli
>
> Here's example output from one of my drives with the above tool:
>
> # nvme smart-log /dev/nvme0
> Smart Log for NVME device:/dev/nvme0 namespace-id:ffffffff
> critical_warning : 0
> temperature : 29 C
> available_spare : 100%
> available_spare_threshold : 10%
> percentage_used : 0%
> data_units_read : 577,600
> data_units_written : 3,182,404
> host_read_commands : 4,537,801
> host_write_commands : 18,713,235
> controller_busy_time : 17
> power_cycles : 1
> power_on_hours : 163
> unsafe_shutdowns : 1
> media_errors : 0
> num_err_log_entries : 0
I wanted to run more stress tests before reporting back.
next prev parent reply other threads:[~2016-01-15 18:18 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 [this message]
2016-01-15 18:20 ` Stephen Hemminger
2016-01-15 21:19 ` Keith Busch
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=20160115101819.2e63b19b@xeon-e3 \
--to=stephen@networkplumber.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