public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-xxxx driver
Date: Thu, 28 Nov 2013 07:59:53 -0500	[thread overview]
Message-ID: <yq1iovclm0m.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAO9zADw-k+Qghk79yzwzaiYiPSoQnKwjjTBwrhcOrJxTWc-fOQ@mail.gmail.com> (Justin Piszcz's message of "Mon, 25 Nov 2013 17:01:12 -0500")

>>>>> "Justin" == Justin Piszcz <jpiszcz@lucidpixels.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

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2013-11-28 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 22:01 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-xxxx driver Justin Piszcz
2013-11-28 12:59 ` Martin K. Petersen [this message]
2013-11-28 13:07   ` Justin Piszcz
2013-11-28 13:13     ` Martin K. Petersen
2013-11-28 21:52       ` Justin Piszcz
2013-12-05 23:43         ` Justin Piszcz
2013-12-06  0:02           ` Greg KH
2013-12-06  0:35           ` Martin K. Petersen

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=yq1iovclm0m.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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