From: lruppert@avalon.syr.edu (Louis Ruppert) Subject: some problems with my linux 0.99pl7 Date: Sat, 1 May 1993 01:06:04 EDT
Lately I've been getting filesystem overflow messages when using Linux with a load of
about 3 mild-mannered users (and X11, and an LPmud). I can't create files and I
often can't get a directory listing. (and I can't pipe). What could be causing this?
Here are my partitions:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hda3 64680 58898 5782 91% /
/dev/hda4 28980 28444 536 98% /tmp_mnt/data
/dev/hda1 97216 87598 9618 90% /tmp_mnt/dos
I checked /dev/hda3 with efsck and it showed that I had plenty of inodes left.
I did the same thing with /dev/hda4 and fsck and it also returned that I had plenty
of inodes left. Shortage of inodes is the only reason I can think of that a
filesystem wouldn't let me create more files.
Also I have been getting messages recently about not being able to start any new
processes. This was with 5 idle xterms and X11 w/olvwm and the kernel compiling in
a virtual console. This is a comparatively light system load for me. Could it be
because of the same problem as above, not being allowed to create any more files?
Thirdly, I have a nasty problem with hung ports, Every time I use term 1.06 the ports
I redirect do not get released when I shut the server down with ^Xes. Whenever I try
to reconnect with term and redirect my port 119 to the campus NNTP server, it tells
me that the port is already bound. I tried removing the $HOME/.term/socket file
and restarting inetd and portmap before connecting and other such voodoo fixes, but
they didn't work. The only reliable way I've found to free up the ports is to
reboot the computer. Is this a common problem with other people or is my computer
just a freakish oddity? Bonus points to whoever can solve this problem.
Thanks in advance for all of your help on these issues,
-Louis Ruppert
lruppert@mailbox.syr.edu