* Re: Multipath issues with kernel device errors
[not found] ` <1188338656.12737.18.camel@linuxchandra>
@ 2007-08-29 6:14 ` Hannes Reinecke
2007-08-29 13:29 ` Jeffry Bilder
2007-08-29 16:58 ` Jeffry Bilder
0 siblings, 2 replies; 4+ messages in thread
From: Hannes Reinecke @ 2007-08-29 6:14 UTC (permalink / raw)
To: device-mapper development
Chandra Seetharaman wrote:
> You do not have the latest table.
> Try with the table below (converted from 0.4.8 version's hwtable.c)
> devices {
> device {
> vendor "COMPAQ"
> product "MSA1000"
> path_grouping_policy group_by_prio
> path_checker tur
> prio_callout "/sbin/mpath_prio_alua /dev/%n"
> getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
> failback immediate
> }
> }
>
Errm. Not quite. My sources indicate that this machine
runs the older active/passive firmware, which requires
the 'hp_sw' hardware handler to run properly.
So better use this:
devices {
device {
vendor "COMPAQ"
product "MSA1000"
hardware_handler "1 hp_sw"
path_grouping_policy group_by_prio
path_checker hp_sw
prio_callout "/sbin/mpath_prio_hp_sw /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
failback manual
}
}
if mpath_prio_hp_sw is missing complain to Ben Marzinski :-)
Alternatively you can use
path_grouping_policy failover
and omit the prio_callout altogether. But then only one path
per SP are used.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Multipath issues with kernel device errors
2007-08-29 6:14 ` Multipath issues with kernel device errors Hannes Reinecke
@ 2007-08-29 13:29 ` Jeffry Bilder
2007-08-29 16:58 ` Jeffry Bilder
1 sibling, 0 replies; 4+ messages in thread
From: Jeffry Bilder @ 2007-08-29 13:29 UTC (permalink / raw)
To: device-mapper development
Thank you!! mpath_prio_hp_sw was certainly missing, so I just used the failover option and commented it out. Those errors are gone now! Thanks so much for your help!
- JB
-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Hannes Reinecke
Sent: Wednesday, August 29, 2007 1:15 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipath issues with kernel device errors
Chandra Seetharaman wrote:
> You do not have the latest table.
> Try with the table below (converted from 0.4.8 version's hwtable.c)
> devices {
> device {
> vendor "COMPAQ"
> product "MSA1000"
> path_grouping_policy group_by_prio
> path_checker tur
> prio_callout "/sbin/mpath_prio_alua /dev/%n"
> getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
> failback immediate
> }
> }
>
Errm. Not quite. My sources indicate that this machine
runs the older active/passive firmware, which requires
the 'hp_sw' hardware handler to run properly.
So better use this:
devices {
device {
vendor "COMPAQ"
product "MSA1000"
hardware_handler "1 hp_sw"
path_grouping_policy group_by_prio
path_checker hp_sw
prio_callout "/sbin/mpath_prio_hp_sw /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
failback manual
}
}
if mpath_prio_hp_sw is missing complain to Ben Marzinski :-)
Alternatively you can use
path_grouping_policy failover
and omit the prio_callout altogether. But then only one path
per SP are used.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Multipath issues with kernel device errors
2007-08-29 6:14 ` Multipath issues with kernel device errors Hannes Reinecke
2007-08-29 13:29 ` Jeffry Bilder
@ 2007-08-29 16:58 ` Jeffry Bilder
2007-10-04 18:49 ` Dave Wysochanski
1 sibling, 1 reply; 4+ messages in thread
From: Jeffry Bilder @ 2007-08-29 16:58 UTC (permalink / raw)
To: device-mapper development
Are the errors in the kernel log normal:
Aug 28 10:30:15 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64229
Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64230
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64231
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64232
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64233
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64234
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64235
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64236
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64237
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64238
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64239
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64240
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64241
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64242
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64243
Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 514064
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64258
Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513680
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64210
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64211
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64212
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64213
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64214
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64215
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64216
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64217
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64218
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64219
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64220
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64221
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64222
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64223
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64224
Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64225
Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
Thanks,
JB
-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of Hannes Reinecke
Sent: Wednesday, August 29, 2007 1:15 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipath issues with kernel device errors
Chandra Seetharaman wrote:
> You do not have the latest table.
> Try with the table below (converted from 0.4.8 version's hwtable.c)
> devices {
> device {
> vendor "COMPAQ"
> product "MSA1000"
> path_grouping_policy group_by_prio
> path_checker tur
> prio_callout "/sbin/mpath_prio_alua /dev/%n"
> getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
> failback immediate
> }
> }
>
Errm. Not quite. My sources indicate that this machine
runs the older active/passive firmware, which requires
the 'hp_sw' hardware handler to run properly.
So better use this:
devices {
device {
vendor "COMPAQ"
product "MSA1000"
hardware_handler "1 hp_sw"
path_grouping_policy group_by_prio
path_checker hp_sw
prio_callout "/sbin/mpath_prio_hp_sw /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
failback manual
}
}
if mpath_prio_hp_sw is missing complain to Ben Marzinski :-)
Alternatively you can use
path_grouping_policy failover
and omit the prio_callout altogether. But then only one path
per SP are used.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Multipath issues with kernel device errors
2007-08-29 16:58 ` Jeffry Bilder
@ 2007-10-04 18:49 ` Dave Wysochanski
0 siblings, 0 replies; 4+ messages in thread
From: Dave Wysochanski @ 2007-10-04 18:49 UTC (permalink / raw)
To: device-mapper development
On Wed, 2007-08-29 at 11:58 -0500, Jeffry Bilder wrote:
> Are the errors in the kernel log normal:
>
>
> Aug 28 10:30:15 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64229
> Aug 28 10:30:15 rac02 kernel: Buffer I/O error on device sdf, logical block 64230
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64231
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64232
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64233
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64234
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64235
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64236
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64237
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64238
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64239
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64240
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64241
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64242
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64243
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513824
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64228
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 514064
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64258
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
> Aug 28 10:30:16 rac02 kernel: end_request: I/O error, dev sdf, sector 513680
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64210
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64211
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64212
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64213
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64214
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64215
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64216
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64217
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64218
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64219
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64220
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64221
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64222
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64223
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64224
> Aug 28 10:30:16 rac02 kernel: Buffer I/O error on device sdf, logical block 64225
> Aug 28 10:30:16 rac02 kernel: Device sdf not ready.
>
>
Yes unfortunately these are normal for this array and any array that has
passive paths. There are fixes needed in the kernel to eliminate these
errors.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-10-04 18:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <8CED8CEBA23FC0409E1A3009F7F47BE502471065@exchange.g2switchworks.com>
[not found] ` <1188333723.12737.7.camel@linuxchandra>
[not found] ` <8CED8CEBA23FC0409E1A3009F7F47BE502471086@exchange.g2switchworks.com>
[not found] ` <1188338656.12737.18.camel@linuxchandra>
2007-08-29 6:14 ` Multipath issues with kernel device errors Hannes Reinecke
2007-08-29 13:29 ` Jeffry Bilder
2007-08-29 16:58 ` Jeffry Bilder
2007-10-04 18:49 ` Dave Wysochanski
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.