From owner-freebsd-questions Mon Apr 9 7:53:25 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by hub.freebsd.org (Postfix) with SMTP id 3577437B422 for ; Mon, 9 Apr 2001 07:53:22 -0700 (PDT) (envelope-from bsd140870@yahoo.co.uk) Received: from unknown (HELO as2.kptn.org) (203.106.173.143) by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Apr 2001 14:53:20 -0000 X-Apparently-From: Date: Mon, 9 Apr 2001 22:46:26 +0800 From: bsd140870 X-Mailer: The Bat! (v1.52 Beta/1) Reply-To: bsd140870 Organization: n/a X-Priority: 3 (Normal) Message-ID: <1195174570.20010409224626@yahoo.co.uk> To: FreeBSD Questions Subject: Re[5]: nfs and cp problem: file system full - SOLVED In-Reply-To: <18438106924.20010409005340@yahoo.co.uk> References: <18438106924.20010409005340@yahoo.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Monday, April 09, 2001, 12:53:40 AM, you wrote: answering to ones own post is not good (i think i read it somewhere) anyways, i solved the problem. it must have been the lack of sleep. it now works... mkdir /usr/portstmp <=== was previously mkdir /portstmp mount as1:/usr/ports /usr/ports cp -R /usr/ports /usr/portstmp / (rootdir) is only 80M and that was why it was full(?) thats my guess anyways. thanks for the help nevertheless. b> Sunday, April 08, 2001, 11:32:46 PM, you wrote: AM>> You are correct, the client shouldn't run out of space. All things being AM>> equal then /usr should have more than enough space for ports. Which AM>> confused me for a while...until I read your original post again a few AM>> times. I think I might have nailed it this time...here goes... >>> p200(as1) as an nfs server and duron650(as3) as an nfs client. nfs >>> mounts ok w/ no problems. >>> >>> mount as1:/usr/ports /portstmp b> wrong. my apologies. that should've been: b> mount as1:/usr/ports /usr/ports b> since there is nothing in /usr/ports on the client (as3). AM>> Assuming you're executing this command on the client (as3) then that AM>> should mount the server's /usr/ports as /portstmp, correct? >>> cp -R /usr/ports/* /portstmp AM>> Also assuming you execute this on the client (as3) then that looks to me AM>> like you're trying to copy everything from the client's /usr/ports/ AM>> directory into /portstmp (which is an nfs mount of the ports collection on AM>> as1). If this is the case then I suspect this isn't what you want to do AM>> and is the reason you are running out of space. AM>> First off you will probably want to kick yourself (I always find it helps AM>> to kick oneself at times like this...and trust me when I say that AM>> everybody on this list has made this kind of mistake many times before) b> it is so true :) again, my mistake. AM>> Once that's done, what I would do, as this will probably have damaged the AM>> ports collection on as1, would be to rm -rf * in /usr/ports on the AM>> client (as3) cvsup the ports on the server (as1) and then execute: AM>> mount as1:/usr/ports /portstmp AM>> cp -R /portstmp/* /usr/ports AM>> on the client (as3). AM>> My apologies for not spotting this earlier. Hope this helps. AM>> Andy AM>> *************************************** AM>> Andrew McKay AM>> Located near Birmingham, England AM>> Catalogue available on request AM>> *************************************** -- bsd140870 mailto:bsd140870@yahoo.co.uk _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message