Also here is the contents of /boot - I am concerned about this symblink: lrwxrwxrwx 1 root root 19 Feb 6 09:27 System.map -> System.map-2.4.7-10 as all the other symblinks ppint to the latest version: <SNIP> [root@ns5 boot]# ls -al total 10908 drwxr-xr-x 3 root root 4096 Feb 6 09:27 . drwxr-xr-x 23 root root 4096 Feb 6 09:56 .. -rw-r--r-- 1 root root 5824 Jun 25 2001 boot.b -rw-r--r-- 1 root root 612 Jun 25 2001 chain.b -rw-r--r-- 1 root root 42268 Nov 14 01:50 config-2.4.18-18.7.x -rw-r--r-- 1 root root 42257 Jan 31 12:20 config-2.4.18-24.7.x drwxr-xr-x 2 root root 4096 Feb 6 09:16 grub -rw-r--r-- 1 root root 126906 Dec 16 10:34 initrd-2.4.18-18.7.x.img -rw-r--r-- 1 root root 127368 Feb 6 09:15 initrd-2.4.18-24.7.x.img -rw-r--r-- 1 root root 337546 Feb 22 2002 initrd-2.4.7-10.img lrwxrwxrwx 1 root root 14 Dec 16 10:33 kernel.h -> kernel.h-2.4.9 -rw-r--r-- 1 root root 405 Dec 16 10:33 kernel.h-2.4.9 -rw-r--r-- 1 root root 23108 Jun 25 2001 message lrwxrwxrwx 1 root root 25 Feb 6 09:15 module-info -> module-info-2.4.18-24.7.x -rw-r--r-- 1 root root 15436 Nov 14 01:50 module-info-2.4.18-18.7.x -rw-r--r-- 1 root root 15436 Jan 31 12:20 module-info-2.4.18-24.7.x -rw-r--r-- 1 root root 13598 Sep 6 2001 module-info-2.4.7-10 -rw-r--r-- 1 root root 640 Jun 25 2001 os2_d.b lrwxrwxrwx 1 root root 19 Feb 6 09:27 System.map -> System.map-2.4.7-10 -rw-r--r-- 1 root root 490460 Nov 14 01:50 System.map-2.4.18-18.7.x -rw-r--r-- 1 root root 490643 Jan 31 12:20 System.map-2.4.18-24.7.x -rw-r--r-- 1 root root 435039 Sep 6 2001 System.map-2.4.7-10 -rwxr-xr-x 1 root root 2983920 Nov 14 01:50 vmlinux-2.4.18-18.7.x -rwxr-xr-x 1 root root 2986554 Jan 31 12:20 vmlinux-2.4.18-24.7.x lrwxrwxrwx 1 root root 21 Feb 6 09:15 vmlinuz -> vmlinuz-2.4.18-24.7.x -rw-r--r-- 1 root root 1064284 Nov 14 01:50 vmlinuz-2.4.18-18.7.x -rw-r--r-- 1 root root 1064546 Jan 31 12:20 vmlinuz-2.4.18-24.7.x -rw-r--r-- 1 root root 802068 Sep 6 2001 vmlinuz-2.4.7-10 </SNIP> Is there some reason why System.map -> System.map-2.4.7-10 instead of System.map-2.4.18-24.7.x ?? Thank you in advance. Regards, Nico Morrison nico.morrison@micronicos.com ___________________________________________ Micronicos Limited - London, UK. Tel: +44 20 8870 8849 Fax: +44 20 8870 5290 ___________________________________________ From: Stephen DeBrass [mailto:debrass@staff.singnet.com.sg] Sent: 06 February 2003 10:20 To: Nico Morrison Cc: 'Stephen C. Tweedie'; 'Andrew Morton'; ext3 users list Subject: RE: On very different journalling activity on 2 servers. On Thu, 6 Feb 2003, Nico Morrison wrote: > Hello, > > I have upgraded the 'bad' machine with the latest 'up2date' kernel, but it > is possible that GRUB is still loading the older kernel. Our sysadmin at the > dayacentre says the console shows the old kernel kernel-2.4.7-10 > > This might have happened because the first kernel upgrade I did on this > machine I did manually by downloading the .rpm & installing it locally. > > Now I know to use /use/sbin/up2date instead but ...... You may need to add an entry to /etc/grub.conf that looks something like: title Red Hat Linux (2.4.19) root (hd0,0) kernel /vmlinuz-2.4.19 ro root=/dev/hda7 I believe grub picks defaults to booting the first entry it finds, someone correct me if I'm wrong, I'm not all too familiar with grub... > How do I tell from the machine (SSH) which kernel it is actually running? uname -a > Thanks - sorry to be so ignorant. No problem :) > Regards, > Nico Morrison > nico.morrison@micronicos.com > ___________________________________________ > Micronicos Limited - London, UK. > Tel: +44 20 8870 8849 Fax: +44 20 8870 5290 > ___________________________________________ > > From: Stephen C. Tweedie [mailto:sct@redhat.com] > Sent: 05 February 2003 10:13 > To: Nico Morrison > Cc: 'Andrew Morton'; ext3 users list > Subject: RE: On very different journalling activity on 2 servers. > > > Hi, > > On Wed, 2003-02-05 at 08:45, Nico Morrison wrote: > > > [root@ns5 nico]# /sbin/hdparm /dev/hda > > /dev/hda: > > using_dma = 0 (off) > > > Does this mean that dma is in fact off? > > Yes. > > > Looks like is ON on the server that has no problems and OFF on the one > with > > loadsa journalling? > > Yes. > > > What do we need to do & is it safe to turn DMA ON on a busy working public > > internet server? > > You don't. > > The trouble is, the kernel usually has a reason for not being in DMA > mode. If it can negotiate DMA, it will; but the older of your two > systems did not do so, so either that older kernel doesn't know how to > drive the IDE controller in DMA mode safely, or it has detected an error > on the IDE bus and has backed off to non-DMA mode automatically. In > both cases, forcing DMA on manually is not recommended. > > I'd suggest that you upgrade the 7.2 box to the current errata kernel, > which is the same across all the 7.* releases. That should give you the > same updated IDE drivers as the 7.3 box has, and will hopefully get you > running DMA properly. If it doesn't, then you're going to have to check > the logs to see why DMA isn't being negotiated. > > Cheers, > Stephen > > > > _______________________________________________ > > Ext3-users@redhat.com > https://listman.redhat.com/mailman/listinfo/ext3-users > _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
