On Thursday, March 9, 2017 6:03:34 PM MST Keith Busch wrote:
> On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote:
> > On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> > >
> > > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb
> > > echo 128 > /sys/block/nvme0n1
On Thu, Mar 09, 2017 at 03:01:27PM -0700, Thomas Fjellstrom wrote:
> On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> >
> > echo 128 > /sys/block/nvme0n1/queue/max_hw_sectors_kb
> > echo 128 > /sys/block/nvme0n1/queue/max_nr_requests
> >
>
> First off, theres no max_nr_requests,
On Monday, March 6, 2017 5:46:33 PM MST Keith Busch wrote:
> On Sun, Mar 05, 2017 at 11:11:45PM -0700, Thomas Fjellstrom wrote:
> > Tonight I decided to try kernel 4.11-rc1. Still getting page allocation
> > failures and aborted nvme commands once iozone gets to the fwrite/fread
> > testing.
> >
>
On Sun, Mar 05, 2017 at 11:11:45PM -0700, Thomas Fjellstrom wrote:
> Tonight I decided to try kernel 4.11-rc1. Still getting page allocation
> failures and aborted nvme commands once iozone gets to the fwrite/fread
> testing.
>
> The taint seems to be comming from previos warnings from the radeon
Tonight I decided to try kernel 4.11-rc1. Still getting page allocation
failures and aborted nvme commands once iozone gets to the fwrite/fread
testing.
The taint seems to be comming from previos warnings from the radeon kernel
driver.
Its a pretty simple: iozone -a -s 64G run.
new log:
[ 57
On Friday, March 3, 2017 8:27:40 AM MST Thomas Fjellstrom wrote:
> I just got a new Samsung 960 Evo 256GB m.2 nvme drive, and put it through
> some tests.
>
> When I run `iozone -a -s 60G` on my desktop (that has 32GB ram and a amd FX
> 8320), i run into some errors. One time the drive completely
6 matches
Mail list logo
