- Community Home
- >
- HPE Community, Korea
- >
- HP-UX
- >
- 급질문입니다 부탁드려요^^;
HP-UX
1752636
회원
5842
온라인
108788
솔루션
포럼
범주
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 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 11-06-2008 11:00 PM
날짜: 11-06-2008 11:00 PM
급질문입니다 부탁드려요^^;
Nov 5 19:42:20 info2 vmunix: msgcnt 13782 vxfs: mesg 003: vx_mapbad - /dev/vg00/lvol5 file system free extent bitmap in au 8 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13786 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 1 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13787 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 6 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13788 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 9 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13789 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 11 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13790 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 12 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13791 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 17 marked bad
syslog에 이러케 나오는데요
bdf 하면
bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 265168 777480 25% /
/dev/vg00/lvol1 524288 116232 404920 22% /stand
/dev/vg00/lvol9 2097152 321922 1667144 16% /var
/dev/vg00/lvol8 3588096 2614802 912515 74% /usr
/dev/vg00/lvol7 1048576 573228 446301 56% /tmp
/dev/vg00/lvol6 3170304 2151317 955360 69% /opt
bdf: /home: I/O error
NAS1:/NFS1/mail 1362558976 482359632 880199344 35% /community/mail
NAS2:/NFS2/BS21DB 1679097856 1309358176 369739680 78% /BS21DB
NAS2:/NFS2/homepage
1679097856 1309358176 369739680 78% /homepage
NAS2:/NFS2/logs 1679097856 1309358176 369739680 78% /logs
/dev/vg00/lvol4 2097152 16982 1950167 1% /CRASH
/dev/vg00/was_lv 2097152 1013620 1015861 50% /WAS
home 부분 lvol5가 io에러가 나요 umount해도 device busy라고 나오고요 disk stale같은건 하나도 없는데요 무슨문제인지 부탁드립니다
Nov 5 19:45:12 info2 vmunix: msgcnt 13786 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 1 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13787 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 6 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13788 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 9 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13789 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 11 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13790 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 12 marked bad
Nov 5 19:45:12 info2 vmunix: msgcnt 13791 vxfs: mesg 057: vx_esum_bad - /dev/vg00/lvol5 file system extent allocation unit summary number 17 marked bad
syslog에 이러케 나오는데요
bdf 하면
bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 265168 777480 25% /
/dev/vg00/lvol1 524288 116232 404920 22% /stand
/dev/vg00/lvol9 2097152 321922 1667144 16% /var
/dev/vg00/lvol8 3588096 2614802 912515 74% /usr
/dev/vg00/lvol7 1048576 573228 446301 56% /tmp
/dev/vg00/lvol6 3170304 2151317 955360 69% /opt
bdf: /home: I/O error
NAS1:/NFS1/mail 1362558976 482359632 880199344 35% /community/mail
NAS2:/NFS2/BS21DB 1679097856 1309358176 369739680 78% /BS21DB
NAS2:/NFS2/homepage
1679097856 1309358176 369739680 78% /homepage
NAS2:/NFS2/logs 1679097856 1309358176 369739680 78% /logs
/dev/vg00/lvol4 2097152 16982 1950167 1% /CRASH
/dev/vg00/was_lv 2097152 1013620 1015861 50% /WAS
home 부분 lvol5가 io에러가 나요 umount해도 device busy라고 나오고요 disk stale같은건 하나도 없는데요 무슨문제인지 부탁드립니다
4 응답 4
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 11-06-2008 11:00 PM
날짜: 11-06-2008 11:00 PM
급질문입니다 부탁드려요^^;
안녕하세요.
아래는 jfs 커널 메세지중 일부입니다.
원인을 보면 사용자가 read/write 중 i/o error 가 일어난것 같습니다.
umount 후 fsck를 돌려보세요.
그후에도 같은 에러가 생기면 disk 교체를 고려하셔야 될것 같습니다.
그럼.
---------------------------------------------------
WARNING: msgcnt x: vxfs: mesg 057:
vx_esum_bad - mount_point file system extent allocation unit summary number
number marked bad
Message 057 Explanation:
An I/O error occurred reading or writing an extent allocation unit summary.
The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag can't be set, the file
system is disabled.
�Action
Check the console log for I/O errors. If the problem is a disk failure, replace
the disk. If the problem is not related to an I/O failure, find out how the
disk became corrupted. If no user or process was writing to the device, report
the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.
아래는 jfs 커널 메세지중 일부입니다.
원인을 보면 사용자가 read/write 중 i/o error 가 일어난것 같습니다.
umount 후 fsck를 돌려보세요.
그후에도 같은 에러가 생기면 disk 교체를 고려하셔야 될것 같습니다.
그럼.
---------------------------------------------------
WARNING: msgcnt x: vxfs: mesg 057:
vx_esum_bad - mount_point file system extent allocation unit summary number
number marked bad
Message 057 Explanation:
An I/O error occurred reading or writing an extent allocation unit summary.
The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag can't be set, the file
system is disabled.
�Action
Check the console log for I/O errors. If the problem is a disk failure, replace
the disk. If the problem is not related to an I/O failure, find out how the
disk became corrupted. If no user or process was writing to the device, report
the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
날짜: 11-06-2008 11:00 PM
날짜: 11-06-2008 11:00 PM
급질문입니다 부탁드려요^^;
안녕하세요.
umount 가 안되고 device busy 라고 나온다는건
누가 쓰고 있다는겁니다.
fuser -cu /home 으로 누가 쓰고 있는지 확인한후
해당 프로세스를 kill 로 죽여보세요.
이 명령어가 안된다면 저같으면
시스템 재부팅이 가능하다는 전제하에 reboot이나 mp 에서
rs 를 치겠습니다. ㅡㅡ;
그럼.
umount 가 안되고 device busy 라고 나온다는건
누가 쓰고 있다는겁니다.
fuser -cu /home 으로 누가 쓰고 있는지 확인한후
해당 프로세스를 kill 로 죽여보세요.
이 명령어가 안된다면 저같으면
시스템 재부팅이 가능하다는 전제하에 reboot이나 mp 에서
rs 를 치겠습니다. ㅡㅡ;
그럼.
위에 명시된 의견은 Hewlett Packard Enterprise가 아닌 저자의 개인 의견입니다. 이 사이트를 사용하면 이용 약관에 동의하게되며 참여 규칙 .
뉴스 및 이벤트
© Copyright 2024 Hewlett Packard Enterprise Development LP