*BSD News Article 64928


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!asstdc.scgt.oz.au!metro!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!imci3!imci4!newsfeed.internetmci.com!news.sprintlink.net!news.dbtech.net!clchapman
From: clchapman@skn.net (Chris Chapman)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: file system full...
Date: Wed, 03 Apr 1996 04:12:55 -0500
Organization: SKNet
Lines: 41
Message-ID: <clchapman-0304960412550001@news.dbtech.net>
NNTP-Posting-Host: ppp11.skn.net
X-Newsreader: Yet Another NewsWatcher 2.2.0b6

As you'll be able to tell as you read further, I'm very new to unix in
general, but prefer to think that I am a fast learner :)  If anyone can
refer me to the resources where I could have found the answer to the
following question on my own that would be great, but please go ahead and
make any suggestions that might rememdy the problem.

We have a p90 with 32mb RAM running BSD/OS 2.0.1.  We constantly receive
the message

(date) (machine) kernel: uid 0 on /tmp : file system full

immediately after this message I issue df and get this information about
the file system:

FIlesystem    1-k blocks    Used    Avail    Capacity     Mounted on
mfs:19          15871        29     15048       0%           /tmp

I also find this information:

ps -aux    (all other processes exluded by me - obviously)

USER   PID  %CPU  %MEM   VSZ   RSS   TT   STAT   STARTED   TIME     COMMAND
root    19   0.0  26.0   741  16556  ??   Ss     2:57pm   18.00   mfs -o rw -s 3

and the line from top yeilds this (taken at a much later time than the
above info so some of these won't match at all)

PID USERNAME PRI NICE  SIZE   RES STATE   TIME   WCPU    CPU COMMAND
19   root     10    0  748K   17M sleep   0:49  0.00%  0.00% mount_mfs

our server reboots because of a panic: page fault every 2 or 3 days also,
i was wondering, and hoping, that the /tmp full error and the page fault
error would be related.  fsck  is run every time our system reboots but I
don't have enough experience with unix to know if an error unfixable by it
would simply cause an error like this without making a filesystem
unmountable

Sorry if I didn't include, or included too much, information.  Any help is
appreciated.

Thanks for your time.