From: axboe@fb.com (Jens Axboe)
Subject: NVM and swap device
Date: Wed, 13 Jan 2016 11:55:41 -0700 [thread overview]
Message-ID: <56969DAD.5050602@fb.com> (raw)
In-Reply-To: <20160113105122.03fb7e63@xeon-e3>
On 01/13/2016 11:51 AM, Stephen Hemminger wrote:
> On Wed, 13 Jan 2016 10:47:40 -0700
> Jens Axboe <axboe@fb.com> wrote:
>
>> On 01/12/2016 08:40 PM, 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.
>>>
>>> I gave up and went back to spinning rust for swap device for stabilty.
>>
>> That's very odd. Why are you suspecting a driver problem? Have you tried
>> to thoroughly beat the device up with normal IO?
>>
>
> I will try it tonight. Do you have a favorite test?
I'd run something that just beats up on it, reads and writes. If you
have fio installed, something ala:
fio --ioengine=libaio --iodepth=8 --direct=1 --bs=4k
--filename=/dev/nvme0n1 --numjobs=4 --norandommap --runtime=1h
--time_based=1 --name=reads --rw=randread --name=writes --rw=randwrite
This will run 4 processes that randomly read from the device, and 4 that
randomly write. Replace /dev/nvme0n1 with your swap partition. The test
will run for 1 hour.
--
Jens Axboe
next prev parent reply other threads:[~2016-01-13 18:55 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 [this message]
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
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=56969DAD.5050602@fb.com \
--to=axboe@fb.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