Re: cvs up, no space left in /tmp
On Mon, 13 Aug 2007, Rickard Dahlstrand wrote: Yes, but on the server. I get the same when using Stackens cvs-mirror. It appears to be broken quite often based on my experiences and what other people have said. -- Antti Harri
Re: cvs up, no space left in /tmp
Am 13.08.2007 um 11:12 schrieb Antti Harri: On Mon, 13 Aug 2007, Rickard Dahlstrand wrote: Yes, but on the server. I get the same when using Stackens cvs- mirror. It appears to be broken quite often based on my experiences and what other people have said. Got the same message, googled and got some hits. If i understand the messages, it means that there are too many open connections to the server ... or something really bad happened. That was what they said. Restarted cvs and it finished without error. gruesse joerg joerch buechner -- Kaum macht mans richtig, schon funktionierts! (busack thomas) --
Re: cvs up, no space left in /tmp
On Thu, 2007-08-09 at 19:36 +0200, Mackan wrote: Hi, For many months, I've had this in root's crontab: # update src tree 0 4 * * * cd /usr/src cvs -q up - rOPENBSD_4_1 -Pd with no problem. For about a week now I get mail from cron about no space left on device. I need some advise on how to find whats wrong. [...] can't create temporary directory /tmp/cvs-serv19063 No space left on device [...] # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/wd0a 147M 37.7M102M27%2208 1699012% / /dev/wd0d 148M104K140M 0% 14 19312 0% /tmp Like, duh, /tmp is full! -- Shawn K. Quinn [EMAIL PROTECTED]
Re: cvs up, no space left in /tmp
Shawn K. Quinn wrote: On Thu, 2007-08-09 at 19:36 +0200, Mackan wrote: Hi, For many months, I've had this in root's crontab: # update src tree 0 4 * * * cd /usr/src cvs -q up - rOPENBSD_4_1 -Pd with no problem. For about a week now I get mail from cron about no space left on device. I need some advise on how to find whats wrong. [...] can't create temporary directory /tmp/cvs-serv19063 No space left on device [...] # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/wd0a 147M 37.7M102M27%2208 1699012% / /dev/wd0d 148M104K140M 0% 14 19312 0% /tmp Like, duh, /tmp is full! Yes, but on the server. I get the same when using Stackens cvs-mirror. Rickard.
Re: cvs up, no space left in /tmp
* Mackan [EMAIL PROTECTED] [070809 14:13]: Hi, For many months, I've had this in root's crontab: # update src tree 0 4 * * * cd /usr/src cvs -q up - rOPENBSD_4_1 -Pd with no problem. For about a week now I get mail from cron about no space left on device. I need some advise on how to find whats wrong. # dmesg OpenBSD 4.1-stable (GENERIC) #0: Sat Jun 9 12:54:39 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC [...] real mem = 1064857600 (1039900K) avail mem = 964227072 (941628K) using 4278 buffers containing 53366784 bytes (52116K) of memory # cd /usr/src cvs -q up -rOPENBSD_4_1 -Pd can't create temporary directory /tmp/cvs-serv19063 No space left on device # df -hi Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/wd0a 147M 37.7M102M27%2208 1699012% / /dev/wd0d 148M104K140M 0% 14 19312 0% /tmp /dev/wd0e 1006M405M551M42% 13289 130965 9% /usr /dev/wd0i 1006M 59.6M896M 6%2874 141380 2% / usr/local /dev/wd0g 2.0G9.3M1.9G 0%1733 266169 1% / usr/obj /dev/wd0h 2.0G194M1.7G10% 81258 18664430% / usr/ports /dev/wd0f 2.0G630M1.3G33% 78418 18948429% / usr/src /dev/wd0j 4.9G787M3.9G16%4819 654635 1% /var /dev/wd0k 214G5.3G198G 3% 58249 28401397 0% / var/www/users I think that is an issue on the server. Here's an alternative that eases the burden on the server and speeds up your local operations. Try using cvsync to get and maintain your own copy of the repository. Then do your cvs co and cvs up operations against it. If your sending back patches based on changes in your cvs tree, just be sure to # cvs -d [EMAIL PROTECTED]:/cvs diff to create your patches. HTH, Jim
Re: cvs up, no space left in /tmp
On Aug 9, 2007, at 9:46 PM, Jim Razmus wrote: * Mackan [EMAIL PROTECTED] [070809 14:13]: Hi, # cd /usr/src cvs -q up -rOPENBSD_4_1 -Pd can't create temporary directory /tmp/cvs-serv19063 No space left on device I think that is an issue on the server. Here's an alternative that eases the burden on the server and speeds up your local operations. Try using cvsync to get and maintain your own copy of the repository. Then do your cvs co and cvs up operations against it. If your sending back patches based on changes in your cvs tree, just be sure to # cvs -d [EMAIL PROTECTED]:/cvs diff to create your patches. HTH, Jim Thanks, I never thought of that the no space left message was from the server side. It isn't obvious. Mackan
