Very Computer

Update on continuing efforts to coax sar on OSR5 to speak to me again:

Based on recent postings by Bela and Charlie, I attempted the following:

        1.  Checked /etc/ps/booted.kernel - it did not exist, so

        2. Ran kernel -uv to recreate it; it errored out with

                kernel: booted inode 4294936250 is not unix
                kernel: booted inode 4294936250 is not unix
                kernel: cannot stat hd(40)unix: no such file or directory
                                                (error 2)

        3.  Tried putting /usr/lib/sa/sar_enable -y in P21perf in /etc/rc2.d
                and rebooted.  Got the same error:

                sar_enable already enabled
                kernel check failed, kernel = (null), code = (Unknown)

Any ideas?          
Lucky

Lucky Leavell                            Phone: (812) 945-6555
Relational Information Systems, Inc.       FAX: (812) 949-9233

New Albany, IN 47150-2013                       71534,2674 (CompuServe)
                                 WWW Home Page:  http://wl.iglou.com/ris

Just a brief public posting to state that my sar is working again!

In the wee small hours this morning, MEGO and all, I noticed the
date/time stamp for /unix was older than it should have been.  I forced
the kernel to relink, rebooted and ... <drum roll> ... sar worked!  Don't
ask me why, it just does!

I did follow Bela and Charlie's suggestions first, so perhaps that did it!

A happy camper,
Lucky

Lucky Leavell                            Phone: (812) 945-6555
Relational Information Systems, Inc.       FAX: (812) 949-9233

New Albany, IN 47150-2013                       71534,2674 (CompuServe)
                                 WWW Home Page:  http://wl.iglou.com/ris

I had a similar problem when I upgraded to OSR5.

I solved it by copying the origional boot file from out in the /var directory
structure to its proper place for booting.

I then rebuilt my kernel and rebooted.

After this the sar_enable -y command worked just fine.

Hope this helps.

Quote:> I had a similar problem when I upgraded to OSR5.

> I solved it by copying the origional boot file from out in the /var directory
> structure to its proper place for booting.

> I then rebuilt my kernel and rebooted.

> After this the sar_enable -y command worked just fine.

The problem is caused by a bug in /boot.  If the kernel's inode number
is >32767, it gets improperly sign extended to 32 bits, which confuses
kernel(ADM) and thus sar(ADM).  The problem only happens on systems with
a combined boot/root filesystem; a fresh install of OpenServer Release 5
uses a separate /stand (/dev/boot) filesystem which has only a few files
and therefore uses only very small inode numbers.

You corrected the problem by relinking the kernel, which happened to get
written with an inode number <32768.  Next time you relink it might come
back.  The same effect could have been achieved by copying /unix over an
existing file with a low inode number (cat /unix > some-other-file),
then renaming it to /unix.

I'm working on a more permanent fix.  Would people who are currently
experiencing the problem please email me directly, and *do not* apply
the workaround I've outlined above.  I need an unspoiled test bed or two
to experiment with.

Quote:>Bela<