Urgent: Too many open files in system

QNX Newsgroups (Archives) qdn.public.qnx4
1

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at www.parse.com
Email my initials at parse dot com.

2

I increased the number of files and OCBs on proc and fsys to a
“huge” number and the problem hasn’t reoccurred since. I’m
wondering if this is a “good” fix…

Here are the values I use now – are they “ok” or will I get into
trouble later?

sys/Proc32
$ 1 Proc32 -f 16 2048 2048

/bin/Fsys
$ 1 Fsys -c64M -f2048

My main question here is, “why now” ? I’m not running anything different
on the system than I was before – just have a bigger disk… That’s
the scary part.

Cheers,
-RK

Robert Krten <nospam91@parse.com> wrote:

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. > :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at > www.parse.com
Email my initials at parse dot com.

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at www.parse.com
Email my initials at parse dot com.

3

I have same problem 2 year ago… butt with disk under 8 GB
and if I remember I was using -f option on Proc32 and some other options…

On default is max open files 2 * max nuber of proceses so I was set bigger
maximum open file on system…

Try monitoring system with osinfo and fsysinfo utilities…

Btw. This my bee one driver/hardvare problem. We will see what say gays from
Hardware Support…

“Robert Krten” <nospam91@parse.com> wrote in message
news:a2ksgc$f4g$1@inn.qnx.com…

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. > :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at
www.parse.com
Email my initials at parse dot com.

4

There used to be an Fsys bug which would cause this, but I thought it
was fixed several patches ago. John Garvey should know - if you have any
influence with him :slight_smile:.

And 2048 is not such a big number. We have exceeded that without hiccups.

Richard

Ernest ©imuniæ wrote:

I have same problem 2 year ago… butt with disk under 8 GB
and if I remember I was using -f option on Proc32 and some other options…

On default is max open files 2 * max nuber of proceses so I was set bigger
maximum open file on system…

Try monitoring system with osinfo and fsysinfo utilities…

Btw. This my bee one driver/hardvare problem. We will see what say gays from
Hardware Support…

“Robert Krten” <> nospam91@parse.com> > wrote in message
news:a2ksgc$f4g$> 1@inn.qnx.com> …

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. > :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at

www.parse.com

Email my initials at parse dot com.

5

Richard R. Kramer <rrkramer@kramer-smilko.com> wrote:

There used to be an Fsys bug which would cause this, but I thought it
was fixed several patches ago. John Garvey should know - if you have any
influence with him > :slight_smile:> .

And 2048 is not such a big number. We have exceeded that without hiccups.

I think the panic has passed – I’ve been running mirror and backrev backups
between the disks and the usual server stuff, and now with the bigger numbers
everything “looks” ok (knock on wood :slight_smile:).

Thanks,
-RK

Richard

Ernest wrote:

I have same problem 2 year ago… butt with disk under 8 GB
and if I remember I was using -f option on Proc32 and some other options…

On default is max open files 2 * max nuber of proceses so I was set bigger
maximum open file on system…

Try monitoring system with osinfo and fsysinfo utilities…

Btw. This my bee one driver/hardvare problem. We will see what say gays from
Hardware Support…

“Robert Krten” <> nospam91@parse.com> > wrote in message
news:a2ksgc$f4g$> 1@inn.qnx.com> …

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. > :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at

www.parse.com

Email my initials at parse dot com.
\

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at www.parse.com
Email my initials at parse dot com.

6

Robert Krten <nospam91@parse.com> wrote:
: I just upgraded my hard disks to 120G, and am now getting “Too Many Open
: Files in System” error messages left right and center.

Internal heap overrun (extra space needed for large bitmaps eats into
ocb, inodes,etc). There will be a ‘traceinfo’ message giving more
details. Either increase the heap size via larger -f/-i values or
use the undocumented -H option to do this (use trace data as size hint).

7

John Garvey <jgarvey@qnx.com> wrote:

Robert Krten <> nospam91@parse.com> > wrote:
: I just upgraded my hard disks to 120G, and am now getting “Too Many Open
: Files in System” error messages left right and center.

Internal heap overrun (extra space needed for large bitmaps eats into
ocb, inodes,etc). There will be a ‘traceinfo’ message giving more
details. Either increase the heap size via larger -f/-i values or
use the undocumented -H option to do this (use trace data as size hint).

Thanks John. I’m glad to know why it did this since I didn’t change what
ran. But the larger bitmaps make sense.

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at www.parse.com
Email my initials at parse dot com.

8

Hi Robert

I think this is related to an undocumented feature in Fsys or one of its
drivers to support very large disks. From memory it was -h or -H something
or other. I also recall that it required a number that needed to be
calculated from a number of attributes. Someone from QSSL will have to
comment.

–
Bill Caroselli – 1(626) 824-7983
Q-TPS Consulting
QTPS@EarthLink.net


“Robert Krten” <nospam91@parse.com> wrote in message
news:a2ksgc$f4g$1@inn.qnx.com…

I just upgraded my hard disks to 120G, and am now getting “Too Many Open
Files in System” error messages left right and center.

Needless to say, I’m dead in the water. > :frowning:

Here’s the partitions:

EIDE 0 (120G)
t77 1G master boot partition
t78 1G Neutrino boot, empty
t79 80G data partition
t80 18G data partition
EIDE 1 (120G)
t77 1G master boot shadow
t78 1G master boot shadow
t79 118G mirror/backup partition

I rebuilt my system with -c64M on the Fsys command line hoping it would
help, but it did not.

I’m using the following versions:

Proc32 4.25L Feb 15 2001
Fsys32 4.24V Feb 18 2000
Fsys.eide 4.25A Feb 09 2000

My Fsys command line in the boot file mounts just the first disk, as
follows:

/bin/Fsys
$ 1 Fsys -c64M

/bin/Fsys.eide
$ 1 Fsys.eide -vv fsys -n0=eide

/bin/mount
$ 1 mount -p /dev/eide0 /dev/eide0t77 / -g

Then later, in my sysinit.1, I mount -p /dev/eide1, and
then mount the partitions under /mount/eide0/t77 etc…

HELP!!!

Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Consulting and Training at
www.parse.com
Email my initials at parse dot com.

9

John Garvey <jgarvey@qnx.com> wrote:

Robert Krten <> nospam91@parse.com> > wrote:
: I just upgraded my hard disks to 120G, and am now getting “Too Many Open
: Files in System” error messages left right and center.

Internal heap overrun (extra space needed for large bitmaps eats into
ocb, inodes,etc). There will be a ‘traceinfo’ message giving more
details. Either increase the heap size via larger -f/-i values or
use the undocumented -H option to do this (use trace data as size hint).

Hi John,

I boosted the -H to 500000; I couldn’t figure out the trace data,
but boosting it to 200000 did not work. Is there any danger with
the value of 500k or is that within the limits of “sane”?

Thanks!
-RK

Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.