> -Original Message-
> From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> Sent: Thursday, November 28, 2013 8:13 AM
>
>
> Martin> http://marc.info/?l=linux-scsi&m=138252394614920&w=2
>
> Justin> Awesome, thank you! This patch is over a month old, do you know
> Justin
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:13 AM
[ .. ]
Martin> http://marc.info/?l=linux-scsi&m=138252394614920&w=2
Justin> Awesome, thank you! This patch is over a month old, do you know
Justin> if is currentl
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:00 AM
To: Justin Piszcz
Cc: open list; linux-e...@vger.kernel.org; linux-scsi@vger.kernel.org
Subject: Re: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-
On Thu, 5 Jul 2007, Bill Davidsen wrote:
Justin Piszcz wrote:
On Wed, 4 Jul 2007, Justin Piszcz wrote:
On Wed, 4 Jul 2007, Michael Tokarev wrote:
> Tejun Heo wrote:
>> Hello,
>>
>> Michael Tokarev wrote:
>>> Well. It looks like the results does
On Wed, 4 Jul 2007, Justin Piszcz wrote:
On Wed, 4 Jul 2007, Michael Tokarev wrote:
> Tejun Heo wrote:
>> Hello,
>>
>> Michael Tokarev wrote:
>>> Well. It looks like the results does not depend on the
>>> elevator. Originally I tried with deadline,
On Wed, 4 Jul 2007, Michael Tokarev wrote:
Tejun Heo wrote:
Hello,
Michael Tokarev wrote:
Well. It looks like the results does not depend on the
elevator. Originally I tried with deadline, and just
re-ran the test with noop (hence the long delay with
the answer) - changing linux elevator ch
My .config is attached.. I cannot reproduce this problem, it only happened
once, but I want to find out how to make sure it does not happen again.
On Thu, 5 Apr 2007, Justin Piszcz wrote:
On Thu, 5 Apr 2007, Justin Piszcz wrote:
http://www.ussg.iu.edu/hypermail/linux/kernel/0701.3/0315
On Thu, 5 Apr 2007, Justin Piszcz wrote:
Had a quick question, this is the first time I have seen this happen, and it
was not even under during heavy I/O, hardly anything was going on with the
box at the time.
.. snip ..
# /usr/bin/time badblocks -b 512 -s -v -w /dev/sdl
Checking for bad
Had a quick question, this is the first time I have seen this happen, and
it was not even under during heavy I/O, hardly anything was going on with
the box at the time.
Any idea what could have caused this? I am running a badblocks test right
now, but so far the disk looks OK.
[369143.91609
9 matches
Mail list logo
