syschk: Overflow usage (93.8%) exceeds 90%

I've resized just about all the files on the system, so what am I
missing here. I take this message to mean that the overflow space is
almost used up. Okay, so what should be done to remedy this?


Thanks,
Danny
Dallas, TX

ddspell-m3 wrote:

You could start by providing some information like:

database product, Version, operating system, etc.

--
Kevin Powick

Kevin Powick wrote:
Running on D3 7.2.1 Linux from Raining Data on Red Hat 7.1 (Seawolf).
ABS patch level is 7.2.1.A96.


Thanks,
Danny

Granted, I am not certain this applies to linux but it may well work.
For D3 on AIX, this is symptomatic of the /var/adm/wtmp file being too
large. Perform the following as root:

cd /var/adm
rm wtmp
touch wtmp

As I said, that works in AIX...not sure about linux.

BTW, hi Danny. I'm not sure you would remember me, but we have an
acquaintance in common in the person of Gil Garcia. I worked with him
briefly in Dallas but I'm now in Wichita, Kansas.

-Bruce Holt


ddspell-m3 wrote:

ddspell-m3 wrote:
This is a d3 message that indicates that your virtual storage space is
almost full.

If it has been a long time since your last save/restore, doing one
might help recover some lost space. Otherwise, you need to delete some
data or increase the amount of space allocated to d3 data files.
Depending on your hardware configuration, adding space might require
hardware additions/changes.

Resizing files often results in better performance, but more space
used, so this does not help.

mvdbman (AT) yahoo (DOT) com wrote:
Hey Bruce,


I remember the name. Can't remember when. Reply to my personal email
and we can catch up.


Regards,
Danny

mvdbman (AT) yahoo (DOT) com wrote:
Well, there's a var directory in the OS, but there isn't any adm
sub-directory.

"ddspell-m3" wrote
near full. The line of stars "*" are sort of like a gas guage on your car,
more stars mean a fuller 'tank' of unused disk space.

Your file resizing will take effect when you next reload your system;
the file-resize verb just makes notes on how to size the files later on,
it doesn't instantly change the space used on disk of each file.
Wrongly-sized files are not the first thing I'd suspect in an over-full
system. Typically they're sized too small, which hurts performance,
instead of too large. If you've done a save lately and let it collect
file statistics, then LIST-FILE-STATS DET-SUPP will show
which accounts are the biggest disk hogs. Omit the DET-SUPP to
see what files are the biggest hogs, but expect dozens or hundreds
of pages of output if you show all accounts w/o DET-SUPP.

One thing that tends to eat up disk space is held print jobs. On all
but the oldest d3 releases, you can treat 'peqs' as a magic disk file,
doing commands like LIST PEQS TOTAL SIZE {result is in bytes,
so drop the last 6 digits for 'megs' of use.}

Enlarging the allocated space can be as easy as editing the file
/usr/lib/pick/pick0 and taking d3 down briefly. Older versions had
a limit of 2.1 gigs for each DISK line.