xfs
[Top] [All Lists]

Re: Kernel naming conventions

To: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>
Subject: Re: Kernel naming conventions
From: George Georgalis <georgw@xxxxxxxxx>
Date: Tue, 19 Nov 2002 15:48:22 -0500
Cc: xfs mailing list <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20021119185620.VQCZ17861.imf07bis.bellsouth.net@TAZ2>
References: <20021119185620.VQCZ17861.imf07bis.bellsouth.net@TAZ2>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Tue, Nov 19, 2002 at 01:56:10PM -0500, Greg Freemyer wrote:
>
>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.


It's hard to debug when things aren't named correctly. ;) 

here's how I would compile multiple instances of the same kernel.
Extract the kernel source in /usr/src patch it and move
/usr/src/linux to /usr/src/linux-2.4.18-xfs-1.1, if I recall correctly
the patch updates ./include/linux/version.h

the process yields thus:

cat /usr/src/linux-2.4.18-xfs-1.1/include/linux/version.h | grep UTS
#define UTS_RELEASE "2.4.18-xfs-1.1"

you could 
cp -rp  /usr/src/linux-2.4.18-xfs-1.1  /usr/src/linux-2.4.18-xfs-1.1b
and change /usr/src/linux-2.4.18-xfs-1.1b/include/linux/version.h
accordingly... then configure (and load appropriate .config) and
make/install everything.... not sure how to help with the cvs version.

// George



-- 
GEORGE GEORGALIS, System Admin/Architect    cell: 347-451-8229 
Security Services, Web, Mail,            mailto:george@xxxxxxxxx 
File, Print, DB and DNS Servers.       http://www.galis.org/george 


<Prev in Thread] Current Thread [Next in Thread>