See http://seer.entsupport.symantec.com/docs/268523.htm
On 8/16/06, Tony T. <[EMAIL PROTECTED]> wrote: > > Occasionally when I reboot a system with VXFS running I see these entries in > /var/adm/messages (Solaris 9, Veritas 3x): > > Aug 13 04:06:26 server vxfs: [ID 702911 kern.warning] WARNING: msgcnt 5 > vxfs: mesg 017: vx_inactive_tran - /app file system inode 79619 marked bad > incore > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 2 offset > 0x00000010 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 4 offset > 0x00000010 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 5 offset > 0x00000010 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 1 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 6 offset > 0x00000010 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 7 offset > 0x00000010 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 2 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 4 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 5 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 1 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 6 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 2 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 7 offset > 0x00000020 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 4 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 5 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 1 offset > 0x00000040 0 2a93abd 0 1f1 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 6 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 2 offset > 0x00000040 0 2fa5339f 0 35 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 7 offset > 0x00000030 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 4 offset > 0x00000040 0 18549289 0 2da > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 5 offset > 0x00000040 0 252f6b24 0 30 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 1 offset > 0x00000050 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 6 offset > 0x00000040 0 34e25e92 0 995 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 2 offset > 0x00000050 0 0 0 0 > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 7 offset > 0x00000040 0 c7f962c 0 a2b > Aug 13 04:06:26 server vxfs: [ID 885974 kern.info] vxfs msgcnt 4 offset > 0x00000050 0 0 0 0 > -- > > Is there cause for alarm here or are these just informational? The file > systems complained about do not seem to have any issues after the reboot > but I would like to know why vxfs is sqwaking about these... > > TIA. > > > _______________________________________________ > Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > > > -- Ilya Voronin <[EMAIL PROTECTED]> http://ivoronin.blogspot.com _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
