[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00c701ceec3a$c8bcfc90$5a36f5b0$@lucidpixels.com>
Date: Thu, 28 Nov 2013 08:07:24 -0500
From: "Justin Piszcz" <jpiszcz@...idpixels.com>
To: "'Martin K. Petersen'" <martin.petersen@...cle.com>
Cc: "'open list'" <linux-kernel@...r.kernel.org>,
<linux-ext4@...r.kernel.org>, <linux-scsi@...r.kernel.org>
Subject: RE: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-xxxx driver
-----Original Message-----
From: Martin K. Petersen [mailto:martin.petersen@...cle.com]
Sent: Thursday, November 28, 2013 8:00 AM
To: Justin Piszcz
Cc: open list; linux-ext4@...r.kernel.org; linux-scsi@...r.kernel.org
Subject: Re: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-xxxx
driver
>>>>> "Justin" == Justin Piszcz <jpiszcz@...idpixels.com> writes:
Justin> Relevant logs: [178339.353519] 3w-sas: scsi0: ERROR:
Justin> (0x03:0x0101): Invalid command opcode:opcode=0x41.
Justin> [178339.353565] sda2: WRITE SAME failed. Manually zeroing.
Justin> Is this something I should be worried about?
No, it just means that your 3ware controller does not handle the WRITE
SAME command and we fall back to manually writing out zeroes.
I posted a patch a while back that prevents WRITE SAME being issued for
controllers that do not pass the commands through to disk directly:
http://marc.info/?l=linux-scsi&m=138252394614920&w=2
[ .. ]
Awesome, thank you! This patch is over a month old, do you know if is
currently in mainline? I'll also update my case with 3ware/LSI.
Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists