home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.admin
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!ucivax!megatek!randy
- From: randy@megatek.com (Randy Davis)
- Subject: DISK LIMIT REACHED
- Message-ID: <1992Nov20.234709.21592@megatek.com>
- Summary: quota's on 4.1.2
- Sender: randy@megatek.com (Randy Davis)
- Reply-To: randy@megatek.com
- Organization: Megatek Corporation, San Diego, California
- Date: Fri, 20 Nov 1992 23:47:09 GMT
- Lines: 30
-
- Has anyone seen this message on a fileserver's console?:
-
- DISK LIMIT REACHED (/filesystem) - WRITE FAILED
-
- If you have, have you succeeded in eradicating it?
-
- We recently upgraded the fileserver that has all the users home
- directories on it to 4.1.2 (probably should have gone to 4.1.3, but
- we don't have the luxury of doing that just yet due to deadlines and
- such). This is a Sun 4/300 CPU system.
-
- This particular filesystem that is constantly reported on the console
- has quota's enabled. As best I can determine, whenever a user hits their
- quota, this message is spit out on the console, and we really COULDN'T
- care less (although it ISN'T put into the messages file - meaning, to me,
- that it is a kernel message, rather than a message sent to syslog). I've
- found the message, in the /sys/sun4/OBJ/quota_ufs.o file:
-
- # egrep "DISK LIMIT REACHED" *
- quota_ufs.o:DISK LIMIT REACHED (%s) - WRITE FAILED
-
- Yet, I have been unsuccessful in getting rid of it. Nor have I found any
- mention of it in the Sun Online Support System patch database.
-
- Any advice/help to help get rid of the message is appreciated...
-
- Randy Davis Email: randy@megatek.com
- Corporate Network and System Administrator megatek!randy@uunet.uu.net
- Megatek Corporation, San Diego, California ucsd!megatek.uucp!randy
-
-