1837976 Members
2767 Online
110124 Solutions
New Discussion

syslog error help !

 
rveri
Super Advisor

syslog error help !

Hi all ,

Here is the syslog error that I got:

-------
Mar 6 00:00:47 ddsrv01 vmunix: vxfs: mesg 017: vx_dirlook - /backup/sssprd/app1 file system inode 670710 marked bad
Mar 6 00:00:47 ddsrv01 vmunix: vxfs: mesg 008: vx_direrr - /backup/sssprd/app1 file system inode 338465 block 3886120 error 6
Mar 6 00:00:48 ddsrv01 vmunix: vxfs: mesg 017: vx_dirlook - /backup/sssprd/app1 file system inode 670711 marked bad
Mar 6 00:00:48 ddsrv01 vmunix: vxfs: mesg 008: vx_direrr - /backup/sssprd/app1 file system inode 338465 block 3886120 error 6
Mar 6 05:14:47 ddsrv01 vmunix: vxfs: mesg 016: vx_ilisterr - /backup/sssprd/app1 file system error reading inode 670710
Mar 6 05:14:47 ddsrv01 vmunix: vxfs: mesg 008: vx_direrr - /backup/sssprd/app1 file system inode 338465 block 3886120 error 6
Mar 6 05:14:47 ddsrv01 vmunix: vxfs: mesg 016: vx_ilisterr - /backup/sssprd/app1 file system error reading inode 670711
Mar 6 05:14:47 ddsrv01 vmunix: vxfs: mesg 008: vx_direrr - /backup/sssprd/app1 file system inode 338465 block 3886120 error 6
---------------------------------------

- I have checked the lvol and found no stale extent.
- Also checked the respective disks of that vg, shows CLAIMED and diskinfo shows correctly.

What could be the cause? and what to be done?
( This appeared only once 20 hrs before.)

Thanks.
2 REPLIES 2
Senthil Kumar .A_1
Honored Contributor

Re: syslog error help !

Hi,

Hope this link might help you,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=13072&admit=-682735245+1141707268095+28353475

Regards,
Senthil Kumar .A
Let your effort be such, the very words to define it, by a layman - would sound like a "POETRY" ;)
Prashanth.D.S
Honored Contributor

Re: syslog error help !

Hi,

Do let me know if this is a cluster server and whether vgimport has been done on this system rescently or any package shutdown was done..

If so happened in a cluster enviornment it will cause this issue can be fixed with fsck on that particular filesystem.

Prashanth