FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Device-mapper Development

 
 
LinkBack Thread Tools
 
Old 02-28-2011, 06:52 PM
Charles Slivkoff
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

I have a MD3200 setup with multipathd running RHEL 5.5.

The array is split into 2 virtual disk, each assigned to one of the RAID
controllers.


I believe I have the drivers setup properly, including scsi_dh_rdac.

multipath.conf has been customized by the Dell software install as follows:

blacklist {
device {
vendor "*"
product "Universal Xport"
}
}
defaults {
user_friendly_names yes
max_fds 8192
}
devices {
device {
vendor "DELL"
product "MD32xxi"
path_grouping_policy group_by_prio
prio rdac
polling_interval 5
path_checker rdac
path-selector "round-robin 0"
hardware_handler "1 rdac"
failback immediate
features "2 pg_init_retries 50"
no_path_retry 30
rr_min_io 100
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
}
device {
vendor "DELL"
product "MD32xx"
path_grouping_policy group_by_prio
prio rdac
polling_interval 5
path_checker rdac
path-selector "round-robin 0"
hardware_handler "1 rdac"
failback immediate
features "2 pg_init_retries 50"
no_path_retry 30
rr_min_io 100
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
}
}


$ multipath -ll mpath8
mpath8 (36842b2b000528f62000005e04d25d3e7) dm-4 DELL,MD32xx
[size=20T][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1
rdac][rw]

\_ round-robin 0 [prio=100][active]
\_ 2:0:0:1 sdf 8:80 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:1 sdc 8:32 [active][ghost]

$ multipath -ll mpath9
mpath9 (36842b2b0005294f9000005da4d25d3fb) dm-5 DELL,MD32xx
[size=20T][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1
rdac][rw]

\_ round-robin 0 [prio=100][active]
\_ 1:0:0:2 sdd 8:48 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:2 sdg 8:96 [active][ghost]


I have LVM striping extents between these two disks. There are 4 10T
lvols, for example:


$ lvdisplay -m /dev/rmane/d01
--- Logical volume ---
LV Name /dev/rmane/d01
VG Name rmane
LV UUID 6sQcuN-AaG7-EaIN-njz1-LHfB-LlWk-SOfZZE
LV Write Access read/write
LV Status available
# open 1
LV Size 10.00 TB
Current LE 1311210
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 65536
Block device 253:8

--- Segments ---
Logical extent 0 to 1311209:
Type striped
Stripes 2
Stripe size 8192 KB
Stripe 0:
Physical volume /dev/dm-4
Physical extents 1311210 to 1966814
Stripe 1:
Physical volume /dev/dm-5
Physical extents 1311210 to 1966814

I am using ext4 in each of the 4 lvols.

Today, I have started coping some data (about 200GB) to one of these
volumes (via rsync) and I've noticed a large number of errors from the
kernel:


Feb 28 14:24:20 rman-ss-03 kernel: FAILED
Feb 28 14:24:20 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Feb 28 14:24:20 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Feb 28 14:24:20 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1


These are repeating every 1-2 seconds (a total of 2526 times) during the
111 minutes it took to complete the copy.



My best efforts of researching this error have lead me to this thread:

https://www.redhat.com/archives/dm-devel/2009-September/msg00311.html


I don't have any issues during boot and I'm not sure where to go from here.

Any suggestions would be appreciated.

Thanks,


-Charles


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-02-2011, 02:35 AM
"Moger, Babu"
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

Charles,
You said "The array is split into 2 virtual disk, each assigned to one of the RAID controllers".
Did you mean you redistributed the two luns(one is owned by controller A and one by controller B)?

It appears that your luns are moving back and forth between two controllers.. You can try setting failback to manual(failback manual). This is not a solution but to understand the problem.

Are you seeing "MODE_SELECT" messages in the logs.. Can you paste snippet of log messages..
Thanks
Babu


________________________________________
From: dm-devel-bounces@redhat.com [dm-devel-bounces@redhat.com] On Behalf Of Charles Slivkoff [slivkoff@cmu.edu]
Sent: Monday, February 28, 2011 1:52 PM
To: dm-devel@redhat.com
Subject: [dm-devel] Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

I have a MD3200 setup with multipathd running RHEL 5.5.

The array is split into 2 virtual disk, each assigned to one of the RAID
controllers.

I believe I have the drivers setup properly, including scsi_dh_rdac.

multipath.conf has been customized by the Dell software install as follows:

blacklist {
device {
vendor "*"
product "Universal Xport"
}
}
defaults {
user_friendly_names yes
max_fds 8192
}
devices {
device {
vendor "DELL"
product "MD32xxi"
path_grouping_policy group_by_prio
prio rdac
polling_interval 5
path_checker rdac
path-selector "round-robin 0"
hardware_handler "1 rdac"
failback immediate
features "2 pg_init_retries 50"
no_path_retry 30
rr_min_io 100
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
}
device {
vendor "DELL"
product "MD32xx"
path_grouping_policy group_by_prio
prio rdac
polling_interval 5
path_checker rdac
path-selector "round-robin 0"
hardware_handler "1 rdac"
failback immediate
features "2 pg_init_retries 50"
no_path_retry 30
rr_min_io 100
prio_callout "/sbin/mpath_prio_rdac /dev/%n"
}
}


$ multipath -ll mpath8
mpath8 (36842b2b000528f62000005e04d25d3e7) dm-4 DELL,MD32xx
[size=20T][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1
rdac][rw]
\_ round-robin 0 [prio=100][active]
\_ 2:0:0:1 sdf 8:80 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:1 sdc 8:32 [active][ghost]

$ multipath -ll mpath9
mpath9 (36842b2b0005294f9000005da4d25d3fb) dm-5 DELL,MD32xx
[size=20T][features=3 queue_if_no_path pg_init_retries 50][hwhandler=1
rdac][rw]
\_ round-robin 0 [prio=100][active]
\_ 1:0:0:2 sdd 8:48 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:2 sdg 8:96 [active][ghost]


I have LVM striping extents between these two disks. There are 4 10T
lvols, for example:

$ lvdisplay -m /dev/rmane/d01
--- Logical volume ---
LV Name /dev/rmane/d01
VG Name rmane
LV UUID 6sQcuN-AaG7-EaIN-njz1-LHfB-LlWk-SOfZZE
LV Write Access read/write
LV Status available
# open 1
LV Size 10.00 TB
Current LE 1311210
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 65536
Block device 253:8

--- Segments ---
Logical extent 0 to 1311209:
Type striped
Stripes 2
Stripe size 8192 KB
Stripe 0:
Physical volume /dev/dm-4
Physical extents 1311210 to 1966814
Stripe 1:
Physical volume /dev/dm-5
Physical extents 1311210 to 1966814

I am using ext4 in each of the 4 lvols.

Today, I have started coping some data (about 200GB) to one of these
volumes (via rsync) and I've noticed a large number of errors from the
kernel:

Feb 28 14:24:20 rman-ss-03 kernel: FAILED
Feb 28 14:24:20 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Feb 28 14:24:20 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Feb 28 14:24:20 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1

These are repeating every 1-2 seconds (a total of 2526 times) during the
111 minutes it took to complete the copy.


My best efforts of researching this error have lead me to this thread:

https://www.redhat.com/archives/dm-devel/2009-September/msg00311.html


I don't have any issues during boot and I'm not sure where to go from here.

Any suggestions would be appreciated.

Thanks,


-Charles


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-02-2011, 05:52 PM
Charles Slivkoff
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

Hello Babu. Thanks for responding.


You said "The array is split into 2 virtual disk, each
assigned to one of the RAID controllers". Did you mean you
redistributed the two luns(one is owned by controller A and one by
controller B)?


Yes. I have assigned 1 LUN to each of the controllers.


It appears that your luns are moving back and forth between two
controllers.. You can try setting failback to manual(failback
manual). This is not a solution but to understand the problem.


I changed to "failback manual" in /etc/multipath.conf and rebooted. I'm
not sure if the reboot was necessary or not. This does not appear to
have changed the behavior.



Are you seeing "MODE_SELECT" messages in the logs.. Can you paste
snippet of log messages..


There are no "MODE_SELECT" messages in syslog. Would these be appearing
elsewhere? The syslog from the last reboot up until I started receiving
the "Illegal Request" messages is available here http://tinypaste.com/f7f413



-Charles

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-02-2011, 06:28 PM
"Moger, Babu"
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Charles Slivkoff
> Sent: Wednesday, March 02, 2011 12:52 PM
> To: dm-devel@redhat.com
> Subject: Re: [dm-devel] Dell MD3200 - sd: Current: sense key: Illegal
> Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
>
> Hello Babu. Thanks for responding.
>
> > You said "The array is split into 2 virtual disk, each
> > assigned to one of the RAID controllers". Did you mean you
> > redistributed the two luns(one is owned by controller A and one by
> > controller B)?
>
> Yes. I have assigned 1 LUN to each of the controllers.
>
> > It appears that your luns are moving back and forth between two
> > controllers.. You can try setting failback to manual(failback
> > manual). This is not a solution but to understand the problem.
>
> I changed to "failback manual" in /etc/multipath.conf and rebooted. I'm
> not sure if the reboot was necessary or not. This does not appear to
> have changed the behavior.
>
> > Are you seeing "MODE_SELECT" messages in the logs.. Can you paste
> > snippet of log messages..
>
> There are no "MODE_SELECT" messages in syslog. Would these be appearing
> elsewhere? The syslog from the last reboot up until I started receiving
> the "Illegal Request" messages is available here
> http://tinypaste.com/f7f413

One of your lun seem to have a problem. See these messages below..

Mar 2 12:43:14 rman-ss-03 kernel: scsi 1:0:0:0: rdac: LUN 0 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:1: rdac: LUN 1 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:2: rdac: LUN 2 (owned)
Mar 2 12:43:14 rman-ss-03 kernel: scsi 2:0:0:0: rdac: LUN 0 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:1: rdac: LUN 1 (owned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:2: rdac: LUN 2 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: rdac: device handler registered

Lun 0 is not owned by any of the controllers also it is not claimed by sd driver for some reason. Can you find out why that happened.. Or you can remove Lun 0 and see if issue goes away..



Looking at these messages below it is not clear which device caused this error..
Mar 2 12:56:51 rman-ss-03 kernel: FAILED
Mar 2 12:56:51 rman-ss-03 kernel: status = 1, message = 00, host = 0, driver = 08
Mar 2 12:56:51 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal Request
Mar 2 12:56:51 rman-ss-03 kernel: <<vendor>> ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1
Mar 2 12:56:51 rman-ss-03 kernel:

Can you please set scsi logging level to 4096(echo 4096 > /proc/sys/dev/scsi/logging_level) and reboot the host.. That would probably give some more info..


>
>
> -Charles


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-02-2011, 09:55 PM
Charles Slivkoff
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

One of your lun seem to have a problem. See these messages below..

Mar 2 12:43:14 rman-ss-03 kernel: scsi 1:0:0:0: rdac: LUN 0 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:1: rdac: LUN 1 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:2: rdac: LUN 2 (owned)
Mar 2 12:43:14 rman-ss-03 kernel: scsi 2:0:0:0: rdac: LUN 0 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:1: rdac: LUN 1 (owned)
Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:2: rdac: LUN 2 (unowned)
Mar 2 12:43:14 rman-ss-03 kernel: rdac: device handler registered

>

Lun 0 is not owned by any of the controllers also it is not claimed

> by sd driver for some reason. Can you find out why that happened..
> Or you can remove Lun 0 and see if issue goes away..

I'm not sure what 1:0:0:0 and 2:0:0:0 are or where they came from. They
show up in lsscsi but there is no sd device assigned to them, obviously.


$ lsscsi
[0:0:32:0] enclosu DP BACKPLANE 1.07 -
[0:2:0:0] disk DELL PERC H700 2.30 /dev/sda
[0:2:1:0] disk DELL PERC H700 2.30 /dev/sdb
[1:0:0:0] disk DELL MD32xx 0770 -
[1:0:0:1] disk DELL MD32xx 0770 /dev/sdc
[1:0:0:2] disk DELL MD32xx 0770 /dev/sdd
[1:0:0:31] disk DELL Universal Xport 0770 /dev/sde
[2:0:0:0] disk DELL MD32xx 0770 -
[2:0:0:1] disk DELL MD32xx 0770 /dev/sdf
[2:0:0:2] disk DELL MD32xx 0770 /dev/sdg
[2:0:0:31] disk DELL Universal Xport 0770 /dev/sdh
[3:0:0:0] cd/dvd TEAC DVD-ROM DV-28SW R.2A /dev/scd0

These LUNs do not exist in the array configuration. I only see LUNs 1,
2, and 31.


The profile saved from my array is here: http://tinypaste.com/73823

I added to /etc/sysctl.conf "dev.scsi.logging_level = 4096" and
rebooted. The new syslog since the boot is here: http://tinypaste.com/5b72b


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-03-2011, 03:32 AM
"Moger, Babu"
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

I looked at your storage profile.. Noticed that your host type setting is wrong.. See below.
Default host OS: Windows (Host OS index 0)
Can you set it to "Linux" and see if your problem goes away. I am yet to look at messages file.. Please try this and let me know..
Thanks
Babu


________________________________________
From: dm-devel-bounces@redhat.com [dm-devel-bounces@redhat.com] On Behalf Of Charles Slivkoff [slivkoff@cmu.edu]
Sent: Wednesday, March 02, 2011 4:55 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

> One of your lun seem to have a problem. See these messages below..
>
> Mar 2 12:43:14 rman-ss-03 kernel: scsi 1:0:0:0: rdac: LUN 0 (unowned)
> Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:1: rdac: LUN 1 (unowned)
> Mar 2 12:43:14 rman-ss-03 kernel: sd 1:0:0:2: rdac: LUN 2 (owned)
> Mar 2 12:43:14 rman-ss-03 kernel: scsi 2:0:0:0: rdac: LUN 0 (unowned)
> Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:1: rdac: LUN 1 (owned)
> Mar 2 12:43:14 rman-ss-03 kernel: sd 2:0:0:2: rdac: LUN 2 (unowned)
> Mar 2 12:43:14 rman-ss-03 kernel: rdac: device handler registered
>
> Lun 0 is not owned by any of the controllers also it is not claimed
> by sd driver for some reason. Can you find out why that happened..
> Or you can remove Lun 0 and see if issue goes away..

I'm not sure what 1:0:0:0 and 2:0:0:0 are or where they came from. They
show up in lsscsi but there is no sd device assigned to them, obviously.

$ lsscsi
[0:0:32:0] enclosu DP BACKPLANE 1.07 -
[0:2:0:0] disk DELL PERC H700 2.30 /dev/sda
[0:2:1:0] disk DELL PERC H700 2.30 /dev/sdb
[1:0:0:0] disk DELL MD32xx 0770 -
[1:0:0:1] disk DELL MD32xx 0770 /dev/sdc
[1:0:0:2] disk DELL MD32xx 0770 /dev/sdd
[1:0:0:31] disk DELL Universal Xport 0770 /dev/sde
[2:0:0:0] disk DELL MD32xx 0770 -
[2:0:0:1] disk DELL MD32xx 0770 /dev/sdf
[2:0:0:2] disk DELL MD32xx 0770 /dev/sdg
[2:0:0:31] disk DELL Universal Xport 0770 /dev/sdh
[3:0:0:0] cd/dvd TEAC DVD-ROM DV-28SW R.2A /dev/scd0

These LUNs do not exist in the array configuration. I only see LUNs 1,
2, and 31.

The profile saved from my array is here: http://tinypaste.com/73823

I added to /etc/sysctl.conf "dev.scsi.logging_level = 4096" and
rebooted. The new syslog since the boot is here: http://tinypaste.com/5b72b

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-03-2011, 03:14 PM
Charles Slivkoff
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

The host type for my host (rman-ss-03) was set to "Linux", BTW.

...
STORAGE ARRAY
Default type: Windows

Default Group

Host: rman-ss-03
Host type: Linux
Interface type: SAS
Host port identifier: 5a:4b:ad:b0:44:65:8e:00
Alias: Port0
Host port identifier: 5a:4b:ad:b0:44:65:60:00
Alias: Port1
...

Regardless, I changed the default host type to "Linux" and rebooted.

No change in behavior. The "phantom" LUNs are still listed and the
errors are still being logged.


$ lsscsi
[0:0:32:0] enclosu DP BACKPLANE 1.07 -
[0:2:0:0] disk DELL PERC H700 2.30 /dev/sda
[0:2:1:0] disk DELL PERC H700 2.30 /dev/sdb
[1:0:0:0] disk DELL MD32xx 0770 -
[1:0:0:1] disk DELL MD32xx 0770 /dev/sdc
[1:0:0:2] disk DELL MD32xx 0770 /dev/sdd
[1:0:0:31] disk DELL Universal Xport 0770 /dev/sde
[2:0:0:0] disk DELL MD32xx 0770 -
[2:0:0:1] disk DELL MD32xx 0770 /dev/sdf
[2:0:0:2] disk DELL MD32xx 0770 /dev/sdg
[2:0:0:31] disk DELL Universal Xport 0770 /dev/sdh
[3:0:0:0] cd/dvd TEAC DVD-ROM DV-28SW R.2A /dev/scd0

$ tail /var/log/messages
Mar 3 11:13:48 rman-ss-03 kernel: FAILED
Mar 3 11:13:48 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Mar 3 11:13:48 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Mar 3 11:13:48 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1

Mar 3 11:13:48 rman-ss-03 kernel:
Mar 3 11:13:53 rman-ss-03 kernel: FAILED
Mar 3 11:13:53 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Mar 3 11:13:53 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Mar 3 11:13:53 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1

Mar 3 11:13:53 rman-ss-03 kernel:



I looked at your storage profile.. Noticed that your host type
setting is wrong.. See below.

> Default host OS: Windows (Host OS index 0)
> Can you set it to "Linux" and see if your problem goes away.

I am yet to look at messages file.. Please try this and let me know..
Thanks Babu



--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-03-2011, 03:47 PM
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

Hi,

I know this is usually a wild goose chase, but what about the controller firmware?
I can see from the profile that the controller FW is 07.70.06.63, while the latest according to the Dell compatibility matrix is 07.75.14.60

Menny

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Charles Slivkoff
Sent: 03 March, 2011 18:14
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

The host type for my host (rman-ss-03) was set to "Linux", BTW.

...
STORAGE ARRAY
Default type: Windows

Default Group

Host: rman-ss-03
Host type: Linux
Interface type: SAS
Host port identifier: 5a:4b:ad:b0:44:65:8e:00
Alias: Port0
Host port identifier: 5a:4b:ad:b0:44:65:60:00
Alias: Port1
...

Regardless, I changed the default host type to "Linux" and rebooted.

No change in behavior. The "phantom" LUNs are still listed and the
errors are still being logged.

$ lsscsi
[0:0:32:0] enclosu DP BACKPLANE 1.07 -
[0:2:0:0] disk DELL PERC H700 2.30 /dev/sda
[0:2:1:0] disk DELL PERC H700 2.30 /dev/sdb
[1:0:0:0] disk DELL MD32xx 0770 -
[1:0:0:1] disk DELL MD32xx 0770 /dev/sdc
[1:0:0:2] disk DELL MD32xx 0770 /dev/sdd
[1:0:0:31] disk DELL Universal Xport 0770 /dev/sde
[2:0:0:0] disk DELL MD32xx 0770 -
[2:0:0:1] disk DELL MD32xx 0770 /dev/sdf
[2:0:0:2] disk DELL MD32xx 0770 /dev/sdg
[2:0:0:31] disk DELL Universal Xport 0770 /dev/sdh
[3:0:0:0] cd/dvd TEAC DVD-ROM DV-28SW R.2A /dev/scd0

$ tail /var/log/messages
Mar 3 11:13:48 rman-ss-03 kernel: FAILED
Mar 3 11:13:48 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Mar 3 11:13:48 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Mar 3 11:13:48 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1
Mar 3 11:13:48 rman-ss-03 kernel:
Mar 3 11:13:53 rman-ss-03 kernel: FAILED
Mar 3 11:13:53 rman-ss-03 kernel: status = 1, message = 00, host = 0,
driver = 08
Mar 3 11:13:53 rman-ss-03 kernel: <6>sd: Current: sense key: Illegal
Request
Mar 3 11:13:53 rman-ss-03 kernel: <<vendor>> ASC=0x94
ASCQ=0x1ASC=0x94 ASCQ=0x1
Mar 3 11:13:53 rman-ss-03 kernel:


> I looked at your storage profile.. Noticed that your host type
> setting is wrong.. See below.
> Default host OS: Windows (Host OS index 0)
> Can you set it to "Linux" and see if your problem goes away.
> I am yet to look at messages file.. Please try this and let me know..
> Thanks Babu


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-03-2011, 07:59 PM
Charles Slivkoff
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

On 03/03/2011 11:47 AM, Menny_Hamburger@Dell.com wrote:


I know this is usually a wild goose chase, but what about the
controller firmware? I can see from the profile that the controller
FW is 07.70.06.63, while the latest according to the Dell
compatibility matrix is 07.75.14.60


I'll look into this next.

On 03/03/2011 01:30 PM, Yanqing_Liu@Dell.com wrote:


It seems that you mapped your LUNs some time after host bootup. That
causes pseudo LUN 0 to be created. If you lay down DM using Dell
software package, please invoke "rescan_dm_devs" for

re-configuration.


I have used "rescan_dm_devs" before. This did not eliminate the pseudo
LUN 0.


I did manage to get rid of them, though, by un-mapping and re-mapping
the array virtual disks as LUNs 0 & 1, instead of LUNs 1 & 2. The
current array profile is here: http://tinypaste.com/64eebb


lsscsi now looks good. See http://tinypaste.com/3580a

Unfortunately, this did not help with the "Illegal Request" messages.

We may need your related kernel message for further analysis. As to
why setting "failback" to manual doesn't work on MD3200, the problem
may be in multipathing daemon, in combination with SAS tranpportation

trearing down all devices immediately after path loss. We've filed a
bugzilla for this.


The latest syslog is here: http://tinypaste.com/87516


BTW, what is your LVM setting for these devices?


The LUNs are each assigned to their own SCSI controller. Both LUNs (PVs)
are members of a single VG. The LVs are striped across the PVs, thus
allowing both paths to be used. The "lvdisplay -m" output is here:
http://tinypaste.com/7c42a




--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 03-04-2011, 03:34 AM
"Moger, Babu"
 
Default Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

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..

________________________________________
From: dm-devel-bounces@redhat.com [dm-devel-bounces@redhat.com] On Behalf Of Charles Slivkoff [slivkoff@cmu.edu]
Sent: Thursday, March 03, 2011 2:59 PM
To: device-mapper development
Subject: Re: [dm-devel] Dell MD3200 - sd: Current: sense key: Illegal Request ASC=0x94 ASCQ=0x1ASC=0x94 ASCQ=0x1

On 03/03/2011 11:47 AM, Menny_Hamburger@Dell.com wrote:
>
> I know this is usually a wild goose chase, but what about the
> controller firmware? I can see from the profile that the controller
> FW is 07.70.06.63, while the latest according to the Dell
> compatibility matrix is 07.75.14.60

I'll look into this next.

On 03/03/2011 01:30 PM, Yanqing_Liu@Dell.com wrote:
>
> It seems that you mapped your LUNs some time after host bootup. That
> causes pseudo LUN 0 to be created. If you lay down DM using Dell
> software package, please invoke "rescan_dm_devs" for
> re-configuration.

I have used "rescan_dm_devs" before. This did not eliminate the pseudo
LUN 0.

I did manage to get rid of them, though, by un-mapping and re-mapping
the array virtual disks as LUNs 0 & 1, instead of LUNs 1 & 2. The
current array profile is here: http://tinypaste.com/64eebb

lsscsi now looks good. See http://tinypaste.com/3580a

Unfortunately, this did not help with the "Illegal Request" messages.

> We may need your related kernel message for further analysis. As to
> why setting "failback" to manual doesn't work on MD3200, the problem
> may be in multipathing daemon, in combination with SAS tranpportation
> trearing down all devices immediately after path loss. We've filed a
> bugzilla for this.

The latest syslog is here: http://tinypaste.com/87516

> BTW, what is your LVM setting for these devices?

The LUNs are each assigned to their own SCSI controller. Both LUNs (PVs)
are members of a single VG. The LVs are striped across the PVs, thus
allowing both paths to be used. The "lvdisplay -m" output is here:
http://tinypaste.com/7c42a



--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 

Thread Tools




All times are GMT. The time now is 07:37 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org