Date: Mon, 20 Jun 2011 12:01:20 +0200 From: Damien Fleuriot <ml@my.gd> To: freebsd-questions@freebsd.org Subject: Re: (no subject) Message-ID: <4DFF1A70.3030300@my.gd> In-Reply-To: <E012414FCF65894B89F69DE76AE15E9905905E67@CPT-EXCH01.int.mtnbusiness.net> References: <E012414FCF65894B89F69DE76AE15E9905905E67@CPT-EXCH01.int.mtnbusiness.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/20/11 10:13 AM, Traiano Welcome wrote: > Hi List > > We have a FreeBSD 6.2-STABLE #0 server running as a general unix shell server. Recently the system has been running at high load (average 8, and cpu 100%), and even more recently we've started seeing the following types of error when we do cvs commits on the system. The system has between 150 to 200 users on it during the day. > > --- > "/: write failed, filesystem is full" > Error: /tmp/file.commit.72971.tmp: No space left on device; /tmp/file.commit.72971.tmp: WARNING: FILE TRUNCATED > --- > > The disks are definitely not full (this shows up in df -hi), both in terms of storage space and inode utilisation. However the cpu utilisation is permanently at 100%, and we're aware of which processes are causing the utilisation. My question is: Is it possible, under some circumstances that cpu starvation could result in the type of "filesystem is full" errors we're seeing above? > > Thanks in Advance, > Traiano Welcome > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Are you really sure your file system is not full ? 1/ sync 2/ df -h 3/ df -i
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DFF1A70.3030300>