HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Multipath with SuSE SLES9 and MSA 1000: scsi r...
Operating System - Linux
1826417
Members
3905
Online
109692
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2007 01:27 AM
02-08-2007 01:27 AM
Multipath with SuSE SLES9 and MSA 1000: scsi reservation conflict
Hi,
i have heavy problems setting up multipath on a SLES9 system.
With multipath -l all devices show only 1 path and they are failed.
Kernel log shows many messages "reservation conflict":
Feb 7 18:56:59 (none) kernel: scsi0 (0,0,18) : reservation conflict
Feb 7 18:56:59 (none) kernel: SCSI error : <0 0 0 18> return code = 0x18
Feb 7 18:56:59 (none) kernel: end_request: I/O error, dev sdb, sector 0
Feb 7 18:56:59 (none) kernel: printk: 1 messages suppressed.
Feb 7 18:56:59 (none) kernel: device-mapper: dm-multipath: 8:16 (#8): IO error - error: -5 - bi_rw: 9 - bi_flags: 18 - bi_error: 01000005
Feb 7 18:56:59 (none) kernel: device-mapper: dm-multipath: Failing path 8:16
Feb 7 18:56:59 (none) multipathd: 8:16: mark as failed
Feb 7 18:56:59 (none) multipathd: dbroutine: remaining active paths: 0
...
Feb 7 18:57:29 (none) multipathd: 8:16: readsector0 checker reports path is up
Feb 7 18:57:29 (none) multipathd: 8:16: reinstated
Feb 7 18:57:29 (none) multipathd: dbroutine: remaining active paths: 1
...
In the attached file you find a configuration summary.
What am I doing wrong?
i have heavy problems setting up multipath on a SLES9 system.
With multipath -l all devices show only 1 path and they are failed.
Kernel log shows many messages "reservation conflict":
Feb 7 18:56:59 (none) kernel: scsi0 (0,0,18) : reservation conflict
Feb 7 18:56:59 (none) kernel: SCSI error : <0 0 0 18> return code = 0x18
Feb 7 18:56:59 (none) kernel: end_request: I/O error, dev sdb, sector 0
Feb 7 18:56:59 (none) kernel: printk: 1 messages suppressed.
Feb 7 18:56:59 (none) kernel: device-mapper: dm-multipath: 8:16 (#8): IO error - error: -5 - bi_rw: 9 - bi_flags: 18 - bi_error: 01000005
Feb 7 18:56:59 (none) kernel: device-mapper: dm-multipath: Failing path 8:16
Feb 7 18:56:59 (none) multipathd: 8:16: mark as failed
Feb 7 18:56:59 (none) multipathd: dbroutine: remaining active paths: 0
...
Feb 7 18:57:29 (none) multipathd: 8:16: readsector0 checker reports path is up
Feb 7 18:57:29 (none) multipathd: 8:16: reinstated
Feb 7 18:57:29 (none) multipathd: dbroutine: remaining active paths: 1
...
In the attached file you find a configuration summary.
What am I doing wrong?
Greetings, Joachim
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2007 02:05 AM
02-08-2007 02:05 AM
Re: Multipath with SuSE SLES9 and MSA 1000: scsi reservation conflict
Shalom,
I card could have gone bad. You may wish to try using ACU 7.55 to boot the system and configure the MSA-1000.
SEP
I card could have gone bad. You may wish to try using ACU 7.55 to boot the system and configure the MSA-1000.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2007 02:20 AM
02-08-2007 02:20 AM
Re: Multipath with SuSE SLES9 and MSA 1000: scsi reservation conflict
> I card could have gone bad. You may wish to try using ACU 7.55 to boot the system and configure the MSA-1000.
Hi Steven,
I do not think a card has gone bad:
1. from MSA 1000 i see both servers on each on both cards
2. on the second linux server i have the same problem
3. In /proc/scsi/qla2xxx/0 and /proc/scsi/qla2xxx/0 i see both cards and i see the connected MSA
4. hwinfo -scsi shows the MSA on both adapters (Number 80 attached to fibrechannel #76 and number 87 attached to fibrechannel #77):
80: SCSI 00.11: 10600 Disk
[Created at block.190]
Unique ID: _q_W.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sda
SysFS BusID: 0:0:0:17
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:17
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sda (/dev/sg1)
Device Number: block 8:0-8:15 (char 21:1)
Geometry (Logical): CHS 34726/64/32
Size: 71119755 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
81: SCSI 00.12: 10600 Disk
[Created at block.190]
Unique ID: R0Fb.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdb
SysFS BusID: 0:0:0:18
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:18
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdb (/dev/sg2)
Device Number: block 8:16-8:31 (char 21:2)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
82: SCSI 00.13: 10600 Disk
[Created at block.190]
Unique ID: uBVf.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdc
SysFS BusID: 0:0:0:19
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:19
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdc (/dev/sg3)
Device Number: block 8:32-8:47 (char 21:3)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
83: SCSI 00.14: 10600 Disk
[Created at block.190]
Unique ID: LNlj.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdd
SysFS BusID: 0:0:0:20
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:20
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdd (/dev/sg4)
Device Number: block 8:48-8:63 (char 21:4)
Geometry (Logical): CHS 34726/64/32
Size: 71119755 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
84: SCSI 00.15: 10600 Disk
[Created at block.190]
Unique ID: oY+n.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sde
SysFS BusID: 0:0:0:21
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:21
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sde (/dev/sg5)
Device Number: block 8:64-8:79 (char 21:5)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
85: SCSI 00.16: 10600 Disk
[Created at block.190]
Unique ID: FkFs.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdf
SysFS BusID: 0:0:0:22
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:22
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdf (/dev/sg6)
Device Number: block 8:80-8:95 (char 21:6)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
86: SCSI 00.0: 10680 Storage Device
[Created at scsi.1464]
Unique ID: uOGh.Iw6w9apFiW8
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /class/scsi_generic/sg0
SysFS BusID: 0:0:0:0
Hardware Class: unknown
Model: "COMPAQ MSA1000"
Vendor: "COMPAQ"
Device: "MSA1000"
Revision: "4.48"
Driver: "qla2400"
Device File: /dev/sg0
Device Files: /dev/sg0, /dev/generic/by-path/pci-0000:13:00.0-scsi-0:0:0:0-generic, /dev/generic/by-id/3500805f3000ac5c0-generic
Device Number: char 21:0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
87: SCSI 100.0: 10680 Storage Device
[Created at scsi.1464]
Unique ID: IwyZ.Iw6w9apFiW8
Parent ID: m862.FrfcNmeLA8B
SysFS ID: /class/scsi_generic/sg7
SysFS BusID: 1:0:0:0
Hardware Class: unknown
Model: "COMPAQ MSA1000"
Vendor: "COMPAQ"
Device: "MSA1000"
Revision: "4.48"
Driver: "qla2400"
Device File: /dev/sg7
Device Files: /dev/sg7, /dev/generic/by-path/pci-0000:16:00.0-scsi-0:0:0:0-generic, /dev/generic/by-id/3500805f3000ac5c0-generic
Device Number: char 21:7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #77 (Fibre Channel)
top
Joachim
Hi Steven,
I do not think a card has gone bad:
1. from MSA 1000 i see both servers on each on both cards
2. on the second linux server i have the same problem
3. In /proc/scsi/qla2xxx/0 and /proc/scsi/qla2xxx/0 i see both cards and i see the connected MSA
4. hwinfo -scsi shows the MSA on both adapters (Number 80 attached to fibrechannel #76 and number 87 attached to fibrechannel #77):
80: SCSI 00.11: 10600 Disk
[Created at block.190]
Unique ID: _q_W.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sda
SysFS BusID: 0:0:0:17
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:17
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sda (/dev/sg1)
Device Number: block 8:0-8:15 (char 21:1)
Geometry (Logical): CHS 34726/64/32
Size: 71119755 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
81: SCSI 00.12: 10600 Disk
[Created at block.190]
Unique ID: R0Fb.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdb
SysFS BusID: 0:0:0:18
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:18
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdb (/dev/sg2)
Device Number: block 8:16-8:31 (char 21:2)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
82: SCSI 00.13: 10600 Disk
[Created at block.190]
Unique ID: uBVf.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdc
SysFS BusID: 0:0:0:19
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:19
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdc (/dev/sg3)
Device Number: block 8:32-8:47 (char 21:3)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
83: SCSI 00.14: 10600 Disk
[Created at block.190]
Unique ID: LNlj.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdd
SysFS BusID: 0:0:0:20
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:20
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdd (/dev/sg4)
Device Number: block 8:48-8:63 (char 21:4)
Geometry (Logical): CHS 34726/64/32
Size: 71119755 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
84: SCSI 00.15: 10600 Disk
[Created at block.190]
Unique ID: oY+n.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sde
SysFS BusID: 0:0:0:21
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:21
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sde (/dev/sg5)
Device Number: block 8:64-8:79 (char 21:5)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
85: SCSI 00.16: 10600 Disk
[Created at block.190]
Unique ID: FkFs.qV34NfZAoJF
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /block/sdf
SysFS BusID: 0:0:0:22
SysFS Device Link: /devices/pci0000:00/0000:00:02.0/0000:13:00.0/host0/0:0:0:22
Hardware Class: disk
Model: "COMPAQ MSA1000 VOLUME"
Vendor: "COMPAQ"
Device: "MSA1000 VOLUME"
Revision: "4.48"
Serial ID: "P56350D9IPC0BT"
Driver: "qla2400", "sd"
Device File: /dev/sdf (/dev/sg6)
Device Number: block 8:80-8:95 (char 21:6)
Geometry (Logical): CHS 36472/255/63
Size: 585922680 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
86: SCSI 00.0: 10680 Storage Device
[Created at scsi.1464]
Unique ID: uOGh.Iw6w9apFiW8
Parent ID: jaVc.FrfcNmeLA8B
SysFS ID: /class/scsi_generic/sg0
SysFS BusID: 0:0:0:0
Hardware Class: unknown
Model: "COMPAQ MSA1000"
Vendor: "COMPAQ"
Device: "MSA1000"
Revision: "4.48"
Driver: "qla2400"
Device File: /dev/sg0
Device Files: /dev/sg0, /dev/generic/by-path/pci-0000:13:00.0-scsi-0:0:0:0-generic, /dev/generic/by-id/3500805f3000ac5c0-generic
Device Number: char 21:0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #76 (Fibre Channel)
87: SCSI 100.0: 10680 Storage Device
[Created at scsi.1464]
Unique ID: IwyZ.Iw6w9apFiW8
Parent ID: m862.FrfcNmeLA8B
SysFS ID: /class/scsi_generic/sg7
SysFS BusID: 1:0:0:0
Hardware Class: unknown
Model: "COMPAQ MSA1000"
Vendor: "COMPAQ"
Device: "MSA1000"
Revision: "4.48"
Driver: "qla2400"
Device File: /dev/sg7
Device Files: /dev/sg7, /dev/generic/by-path/pci-0000:16:00.0-scsi-0:0:0:0-generic, /dev/generic/by-id/3500805f3000ac5c0-generic
Device Number: char 21:7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #77 (Fibre Channel)
top
Joachim
Greetings, Joachim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2007 03:37 AM
02-19-2007 03:37 AM
Re: Multipath with SuSE SLES9 and MSA 1000: scsi reservation conflict
Solved - see http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1098737
Greetings, Joachim
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP