rbriber@POLY1.NIST.GOV (04/10/91)
Here's what should be a simple question. SYSLOG contains the following error about once a day: Apr 8 18:03:02 poly2 grcond[7495]: CIO: t of space Apr 8 18:03:02 poly2 grcond[7495]: CIO: dks0d1s6: Out of space Apr 8 18:03:02 poly2 last message repeated 16 times yet df reports that none of the file systems are particularly full: Filesystem Type blocks use avail %use Mounted on /dev/root efs 30672 20948 9724 68% / /dev/usr efs 1886115 803203 1082912 43% /usr /debug dbg 111912 11464 100448 10% /debug + some nfs mounted stuff which should not be important. Is there away to tell which disk (i.e. which filesystem) belongs to dks0d1s6? (i.e. root or usr? or does this make sense?) Why does it say it's full? The users haven't noticed any particular problems recently that would make me think "uh-oh full disk".... This is on a 4D25 with a 1Gb drive running 3.3.1. ------------------------------------------------------------------------ | Adios Amebas, |"In the future we will all have names that will | | Robert Briber | make the cathode ray tube resonate." | | NIST 224/B210 | --Professor Brian O'Blivion | | Gaithersburg, MD 20899| rbriber@poly1.nist.gov (Internet) | | (301) 975-6775 (voice)| rbriber@enh.nist.gov (Internet) | | (301) 975-2128 (fax) | rbriber@nbsenh.bitnet (Bitnet) | ------------------------------------------------------------------------
samlb@pioneer.arc.nasa.gov (Sam Bassett RCS) (04/10/91)
I just went over to our IRIS and checked -- dsk0d1s6 is /dev/usr (I first looked for the Major & Minor numbers in /dev/dsk [23, 38], then looked at /dev/root and /dev/user -- bingo) We had a similar problem with one machine where /tmp was _NOT_ sym-linked to /usr/tmp, and editor /tmp/Re.... files filled up the root partition -- of course, when you get an error message and drop out of vi, it cleans up its temp files, and nothing appears. Just what were your users doing to fill up that mucking huge /usr partition?? Sam'l Bassett, Sterling Software @ NASA Ames Research Center, Moffett Field CA 94035 Work: (415) 604-4792; Home: (415) 969-2644 samlb@well.sf.ca.us samlb@ames.arc.nasa.gov <Disclaimer> := 'Sterling doesn't _have_ opinions -- much less NASA!'
laplante@ocgy.ubc.ca (Denis Laplante) (04/11/91)
In article <9104091950.AA09095@poly1.nist.gov>, rbriber@POLY1.NIST.GOV writes: |> Here's what should be a simple question. SYSLOG contains the following |> error about once a day: |> |> Apr 8 18:03:02 poly2 grcond[7495]: CIO: t of space |> Apr 8 18:03:02 poly2 grcond[7495]: CIO: dks0d1s6: Out of space |> Apr 8 18:03:02 poly2 last message repeated 16 times |> You should ignore most messages in SYSLOG of the form 'grcond[....]: CIO' , as they are redundant copies of messages reported previously. On the 3 SGI systems I know, similar spurious messages appear everytime someone logs out. I have an awk script to filter out uninteresting SYSLOG messages.
andru@electron.lcs.mit.edu (Andrew Myers) (04/14/91)
laplante@ocgy.ubc.ca (Denis Laplante) writes: > rbriber@POLY1.NIST.GOV writes: >|> Apr 8 18:03:02 poly2 grcond[7495]: CIO: t of space >|> Apr 8 18:03:02 poly2 grcond[7495]: CIO: dks0d1s6: Out of space >|> Apr 8 18:03:02 poly2 last message repeated 16 times >You should ignore most messages in SYSLOG of the form 'grcond[....]: CIO' , >as they are redundant copies of messages reported previously. Not true. A message of the form "grcond: [...] CIO: ..." is a message which would have appeared on the console, if there had been a console. However, this message was generated while there was no console to print it to, either because the console window was closed, or because graphical login is running. Instead, the "graphics console daemon" (grcond) intercepted the message and put it in SYSLOG. While the message may indeed be identical to messages which were previously reported to the console or to SYSLOG, it is not necessarily redundant. Andrew