Linux Device Mapper development
 help / color / mirror / Atom feed
From: Charles Slivkoff <slivkoff@cmu.edu>
To: dm-devel@redhat.com
Subject: Re: Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
Date: Fri, 04 Mar 2011 12:34:07 -0500	[thread overview]
Message-ID: <4D71228F.3020700@cmu.edu> (raw)
In-Reply-To: <E463DF2B2E584B4A82673F53D62C2EF4FF56B44B@cosmail01.lsi.com>

The lvols are EXT4, and I see that barrier is enabled by-default. I can 
try disabling, but need to investigate a bit.

Also, I believe I may have isolated the problem a bit. I can only cause 
this behavior when I access these volumes from an NFS client.

I think this might be put it out of scope of the dm code.


-Charles



On 3/3/11 23:34 , Moger, Babu wrote:
> I have looked at your logs.. Here are the messages..
>
> Mar  3 15:38:37 rman-ss-03 kernel: sd 1:0:0:0: Done: SUCCESS
> Mar  3 15:38:37 rman-ss-03 kernel:         2 sd 1:0:0:0:
> Mar  3 15:38:37 rman-ss-03 kernel:         command: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00
> Mar  3 15:38:37 rman-ss-03 kernel: : Current: sense key: Illegal Request
> Mar  3 15:38:37 rman-ss-03 kernel:<<vendor>>  ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
> Mar  3 15:38:37 rman-ss-03 kernel:
> Mar  3 15:38:38 rman-ss-03 kernel: sd 1:0:0:0: Done: SUCCESS
> Mar  3 15:38:38 rman-ss-03 kernel:         2 sd 1:0:0:0:
> Mar  3 15:38:38 rman-ss-03 kernel:         command: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00
> Mar  3 15:38:38 rman-ss-03 kernel: : Current: sense key: Illegal Request
> Mar  3 15:38:38 rman-ss-03 kernel:<<vendor>>  ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
>
> These messages are coming  because of Synchronize Cache commands.  It
> may be related to type of filesystem you are on. Did you have barrier
> enabled on your filesystem. I see that these commands are going out
> to target on passive paths.. I dont understand that part yet.
> Normally scsi device handlers block commands going out passive
> paths..This should be coming in a differrent path.. I still have to
> figure that out..
>

      reply	other threads:[~2011-03-04 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 19:52 Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1 Charles Slivkoff
2011-03-02  3:35 ` Moger, Babu
2011-03-02 18:52 ` Charles Slivkoff
2011-03-02 19:28   ` Moger, Babu
2011-03-02 22:55   ` Charles Slivkoff
2011-03-03  4:32     ` Moger, Babu
2011-03-03 16:14     ` Charles Slivkoff
2011-03-03 16:47       ` Menny_Hamburger
2011-03-03 20:59         ` Charles Slivkoff
2011-03-04  4:34           ` Moger, Babu
2011-03-04 17:34             ` Charles Slivkoff [this message]

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=4D71228F.3020700@cmu.edu \
    --to=slivkoff@cmu.edu \
    --cc=dm-devel@redhat.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