- Community Home
- >
- HPE Community, Korea
- >
- HP-UX
- >
- 에러내용좀 봐주세요...부탁드립니다.
HP-UX
1753479
회원
4688
온라인
108794
솔루션
포럼
범주
Company
Local Language
뒤로
포럼
토론 게시판
포럼
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
토론 게시판
토론 게시판
포럼
토론 게시판
뒤로
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
블로그
정보
커뮤니티 언어
언어
포럼
블로그
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 12-28-2007 11:00 PM
날짜: 12-28-2007 11:00 PM
에러내용좀 봐주세요...부탁드립니다.
안녕하세요....제가 HP rp3440 장비를 맡고 있는데요...
DB서버인데 스토리지에 SAN으로 연결되어있습니다. HBA카드가 2개 부착하여 서비스에는 영향이 없지만
SAN쪽 담당자는 SAN쪽에는 문제가 없다고 하는데...
syslog.log 파일에 이런 메세지가 나오고 있어서 고수님들에 의견을 듣고 싶습니다.
1. 이런현상이 왜 일어나는지?
2. 조치방안은 모가 있는지?
고수님들 도와주십시요...
<메세지>
Dec 27 15:11:10 IADB02 vmunix: SCSI: Read error -- dev: b 31 0x040300, errno: 126, resid: 1024,
Dec 27 15:11:10 IADB02 vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 1024.
Dec 27 15:11:11 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004f2c2000), from raw device 0x1f040100 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050100 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:11 IADB02 vmunix: LVM: VG 64 0x020000: PVLink 31 0x040100 Failed! The PV is not accessible.
Dec 27 15:11:18 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b662000), from raw device 0x1f040300 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050300 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:18 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b5e8000), from raw device 0x1f040500 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050500 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:18 IADB02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x040300 Failed! The PV is still accessible.
Dec 27 15:11:18 IADB02 vmunix: LVM: VG 64 0x010000: PVLink 31 0x040500 Failed! The PV is still accessible.
Dec 27 15:11:23 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b662000), from raw device 0x1f050300 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040300 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:23 IADB02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x040300 Recovered.
Dec 27 15:11:23 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b5e8000), from raw device 0x1f050500 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040500 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:23 IADB02 vmunix: LVM: VG 64 0x010000: PVLink 31 0x040500 Recovered.
Dec 27 15:11:43 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004f2c2000), from raw device 0x1f050100 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040100 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:43 IADB02 vmunix: LVM: VG 64 0x020000: PVLink 31 0x040100 Recovered.
DB서버인데 스토리지에 SAN으로 연결되어있습니다. HBA카드가 2개 부착하여 서비스에는 영향이 없지만
SAN쪽 담당자는 SAN쪽에는 문제가 없다고 하는데...
syslog.log 파일에 이런 메세지가 나오고 있어서 고수님들에 의견을 듣고 싶습니다.
1. 이런현상이 왜 일어나는지?
2. 조치방안은 모가 있는지?
고수님들 도와주십시요...
<메세지>
Dec 27 15:11:10 IADB02 vmunix: SCSI: Read error -- dev: b 31 0x040300, errno: 126, resid: 1024,
Dec 27 15:11:10 IADB02 vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 1024.
Dec 27 15:11:11 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004f2c2000), from raw device 0x1f040100 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050100 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:11 IADB02 vmunix: LVM: VG 64 0x020000: PVLink 31 0x040100 Failed! The PV is not accessible.
Dec 27 15:11:18 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b662000), from raw device 0x1f040300 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050300 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:18 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b5e8000), from raw device 0x1f040500 (wit
h priority: 0, and current flags: 0x40) to raw device 0x1f050500 (with priority: 1, and current flags: 0x0).
Dec 27 15:11:18 IADB02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x040300 Failed! The PV is still accessible.
Dec 27 15:11:18 IADB02 vmunix: LVM: VG 64 0x010000: PVLink 31 0x040500 Failed! The PV is still accessible.
Dec 27 15:11:23 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b662000), from raw device 0x1f050300 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040300 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:23 IADB02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x040300 Recovered.
Dec 27 15:11:23 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004b5e8000), from raw device 0x1f050500 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040500 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:23 IADB02 vmunix: LVM: VG 64 0x010000: PVLink 31 0x040500 Recovered.
Dec 27 15:11:43 IADB02 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004f2c2000), from raw device 0x1f050100 (wit
h priority: 1, and current flags: 0x0) to raw device 0x1f040100 (with priority: 0, and current flags: 0x80).
Dec 27 15:11:43 IADB02 vmunix: LVM: VG 64 0x020000: PVLink 31 0x040100 Recovered.
2 응답 2
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 12-31-2007 11:00 PM
날짜: 12-31-2007 11:00 PM
에러내용좀 봐주세요...부탁드립니다.
안녕하십니까
로그을 보니 Data가 사용중인 alternate Path로 패스가 변경되는 현상이 자주 일어 나는것 같습니다.
primary Path에 이상이 생길때 Pvlink에 의해 alternate Path로 넘어가게 됩니다. 현재 pvdsiplay 로 보시면 timeout 이 O로 되어 있을것인데 이것을 바꾸십시오
# pvchange -t 180 /dev/dsk/c4t0d5
그리고 현재 pvlink 구성이 엇갈리게 되어 있는지 확인하십시오
예)
vg01
/dev/dsk/c4t0d0
/dev/dsk/c6t0d0
vg02
/dev/dsk/c6t0d1
/dev/dsk/c4t0d1
...
...
스토리지가 무엇인지는 모르겠지만 Failover가 아닌 로드발란싱으로 바꾸는것을 권장합니다.
스토리지나 HBA에 이상이 없다면 I/O가 한쪽으로 너무몰려 이런증상이 나타나는 것 같습니다.
로그을 보니 Data가 사용중인 alternate Path로 패스가 변경되는 현상이 자주 일어 나는것 같습니다.
primary Path에 이상이 생길때 Pvlink에 의해 alternate Path로 넘어가게 됩니다. 현재 pvdsiplay 로 보시면 timeout 이 O로 되어 있을것인데 이것을 바꾸십시오
# pvchange -t 180 /dev/dsk/c4t0d5
그리고 현재 pvlink 구성이 엇갈리게 되어 있는지 확인하십시오
예)
vg01
/dev/dsk/c4t0d0
/dev/dsk/c6t0d0
vg02
/dev/dsk/c6t0d1
/dev/dsk/c4t0d1
...
...
스토리지가 무엇인지는 모르겠지만 Failover가 아닌 로드발란싱으로 바꾸는것을 권장합니다.
스토리지나 HBA에 이상이 없다면 I/O가 한쪽으로 너무몰려 이런증상이 나타나는 것 같습니다.
위에 명시된 의견은 Hewlett Packard Enterprise가 아닌 저자의 개인 의견입니다. 이 사이트를 사용하면 이용 약관에 동의하게되며 참여 규칙 .
뉴스 및 이벤트
© Copyright 2024 Hewlett Packard Enterprise Development LP