I have 2 kernels that I am using on a test server.
One is CVS from Sept. 6, the other is a recent kernel.
The older one is /boot/vmlinuz-2.4.19-xfs2 and has associated map file
System.map-2.4.19-xfs2.
The recent cvs kernel I inadvertently named /boot/vmlinuz-2.4.19-xfs and has
associated map file System.map-2.4.19-xfs.
I know the new one is actually 2.4.20-rc1, but I was not too worried about the
above misnaming.
I have been running the older kernel (xfs2) for the last few days.
At 1:15am every night I initiate a snapshot and mount it for backing up.
Last night my test server locked up and in the warn log I have:
Nov 19 01:15:00 TruStore1000 kernel: XFS mounting filesystem sd(8,17)
Nov 19 01:15:00 TruStore1000 kernel: Symbol table has incorrect version number.
Nov 19 01:15:00 TruStore1000 kernel: Cannot find map file.
Nov 19 01:15:39 TruStore1000 kernel: XFS mounting filesystem lvm(58,3)
I don't know if the above had anything to do with the lockup, but I'm concerned
about why my xfs2 kernel was apparently using the symbol table for my xfs
kernel.
Also important, when I get a lockup I normally end up in kdb automatically.
This time I did not, and I could not figure out to bring it up.
Thanks
Greg
=======
Greg Freemyer
Internet Engineer
Deployment and Integration Specialist
Compaq ASE - Tru64 v4, v5
Compaq Master ASE - SAN Architect
The Norcross Group
www.NorcrossGroup.com
|