Re: /: write failed, filesystem is full
On 5 Sep 2008, at 04:34 , Gautham Ganapathy wrote: As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full I used to get the same error on freebsd 7.0-release if the bsd partition was not aligned to cylinder boundaries. did sysinstall give any warnings about this when you partitioned your harddrive? No, there was no warning about alignment. Only warning was about disk geometry. I tried to install FreeBSD couple of times, and third time it worked like charm :) No warning, no errors. Since I have two machines which are the same, I will try the second one today. Cheers, Nikola ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
I suppose you are downloading some files from ftp to your home. Is that is the case - then you should check where is your home directory. I suppose you do it as root, and the root home is /root, which resides on the / mount. Regards, Ivailo Tanusheff Nikola Knežević [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03.09.2008 21:41 To freebsd-questions@freebsd.org cc Subject /: write failed, filesystem is full Hi, I'm trying to install FreeBSD 7.0 on our new server (Intel Xeon 2x4- core machine), which has a 250GB SATAII disk. I used -bootonly CD image, and assigned whole disk to FreeBSD. Breakdown is: / - 2GB swap - 4GB /var - 9GB /tmp - 4GB /usr - 213GB As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full This shouldn't happen, since sysinstall did newfs on these partitions. What to do? I'll now try to run livefs disk, to see what is happening there. Cheers, Nikola ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
Polytropon wrote: On Wed, 3 Sep 2008 17:30:58 +0200, Nikola Knežević [EMAIL PROTECTED] wrote: Hi, I'm trying to install FreeBSD 7.0 on our new server (Intel Xeon 2x4- core machine), which has a 250GB SATAII disk. I used -bootonly CD image, and assigned whole disk to FreeBSD. Breakdown is: / - 2GB swap - 4GB /var - 9GB /tmp - 4GB /usr - 213GB As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full This shouldn't happen, since sysinstall did newfs on these partitions. What to do? Something went wrong when specifying the disks where the OS is to be installed to. As it has already been mentioned, / is placed on a RAM disk. Extraction of the OS's components has to go to the mountpoints where your correctly created partitions reside (which are more than big enough, especially regarding /, I think). Did you do the installation via the sysinstall utility? If not, make sure the correct mount points are given for the software installation, e. g. /dev/ad0s1a - /mnt/ /dev/ad0s1d - /mnt/tmp /dev/ad0s1e - /mnt/var /dev/ad0s1f - /mnt/usr /dev/ad0s1g - /mnt/home The structures in / (/bin, /usr/local etc.) are not the structures you want to have on the disk you're installing on. PS. Where's your /home partition? :-) There used to be an issue with the installer that if you crashed out of the install process somewhere then restarted it from within sysinstall without rebooting you could get a similar issue. Maybe it's been fixed by now though. Sorry not to be more specific, it's been a long time since it has happened to me, maybe someone who knows more could confirm. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/: write failed, filesystem is full
Hi, I'm trying to install FreeBSD 7.0 on our new server (Intel Xeon 2x4- core machine), which has a 250GB SATAII disk. I used -bootonly CD image, and assigned whole disk to FreeBSD. Breakdown is: / - 2GB swap - 4GB /var - 9GB /tmp - 4GB /usr - 213GB As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full This shouldn't happen, since sysinstall did newfs on these partitions. What to do? I'll now try to run livefs disk, to see what is happening there. Cheers, Nikola ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 3 Sep 2008, Nikola Knežević wrote: Hi, I'm trying to install FreeBSD 7.0 on our new server (Intel Xeon 2x4-core machine), which has a 250GB SATAII disk. I used -bootonly CD image, and assigned whole disk to FreeBSD. Breakdown is: / - 2GB swap - 4GB /var - 9GB /tmp - 4GB /usr - 213GB As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full at install disk / is ramdisk. something is wrong there. while i do prefer single partition+swap setup, your is fine.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 3 Sep 2008 17:30:58 +0200, Nikola Knežević [EMAIL PROTECTED] wrote: Hi, I'm trying to install FreeBSD 7.0 on our new server (Intel Xeon 2x4- core machine), which has a 250GB SATAII disk. I used -bootonly CD image, and assigned whole disk to FreeBSD. Breakdown is: / - 2GB swap - 4GB /var - 9GB /tmp - 4GB /usr - 213GB As soon as I start copying files from FTP, this is the error I get: /: write failed, filesystem is full This shouldn't happen, since sysinstall did newfs on these partitions. What to do? Something went wrong when specifying the disks where the OS is to be installed to. As it has already been mentioned, / is placed on a RAM disk. Extraction of the OS's components has to go to the mountpoints where your correctly created partitions reside (which are more than big enough, especially regarding /, I think). Did you do the installation via the sysinstall utility? If not, make sure the correct mount points are given for the software installation, e. g. /dev/ad0s1a - /mnt/ /dev/ad0s1d - /mnt/tmp /dev/ad0s1e - /mnt/var /dev/ad0s1f - /mnt/usr /dev/ad0s1g - /mnt/home The structures in / (/bin, /usr/local etc.) are not the structures you want to have on the disk you're installing on. PS. Where's your /home partition? :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Suppressing write failed, filesystem is full
Hi, I currently have a virtual domain server that has a couple of jails together on a single server. Unfortunately, I'm stuck with a few others that don't manage their space well and I constantly get: /usr/jail/...: write failed, filesystem is full I happen to also do some amount of development / configuration on the server and seeing those message consistently popping up is just horribly obnoxious. Is there a way I can suppress those messages? I tried asking the sys admins and they claim to be unable to do anything and must wait for the other clients to free up some space. - Mifrai _ Discover sweet stuff waiting for you at the Messenger Cafe. Claim your treat today! http://www.cafemessenger.com/info/info_sweetstuff.html?ocid=TXT_TAGHM_SeptHMtagline2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Suppressing write failed, filesystem is full
On Tuesday 11 September 2007 03:33:29 Micheal Fria wrote: I currently have a virtual domain server that has a couple of jails together on a single server. Unfortunately, I'm stuck with a few others that don't manage their space well and I constantly get: /usr/jail/...: write failed, filesystem is full I happen to also do some amount of development / configuration on the server and seeing those message consistently popping up is just horribly obnoxious. Is there a way I can suppress those messages? I tried asking the sys admins and they claim to be unable to do anything and must wait for the other clients to free up some space. /etc/syslog.conf: *.err;kern.warning;auth.notice;mail.crit/dev/console Remove the offending factility, note that you'll also not get any messages in the same category. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/tmp write failed, filesystem is full
Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
Just run an MFS /tmp, add to fstab(5) then mount /tmp md/tmpmfs rw,-s64m,-m02 0 Let me know if the syntax error persists. ~BAS On Tue, 2007-03-27 at 16:17 +0200, Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
On Tuesday 27 March 2007 09:17:07 am Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele Perhaps /var is getting full also? Rather that soft-linking, I think I'd first try to flush out the /tmp filesystem. -- Three minutes' thought would suffice to find this out; but thought is irksome and three minutes is a long time. -- A. E. Houseman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
David J Brooks [EMAIL PROTECTED] writes: On Tuesday 27 March 2007 09:17:07 am Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele Perhaps /var is getting full also? Rather that soft-linking, I think I'd first try to flush out the /tmp filesystem. Not to mention that the command as shown would make the link in the wrong direction, leaving the builds still using the real /tmp. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
touche... :-) thanks On 3/27/07, Lowell Gilbert [EMAIL PROTECTED] wrote: David J Brooks [EMAIL PROTECTED] writes: On Tuesday 27 March 2007 09:17:07 am Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele Perhaps /var is getting full also? Rather that soft-linking, I think I'd first try to flush out the /tmp filesystem. Not to mention that the command as shown would make the link in the wrong direction, leaving the builds still using the real /tmp. -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
No, /var isn't getting full. i just use 2% of ~1 Gb free. On 3/27/07, Brian A. Seklecki [EMAIL PROTECTED] wrote: Just run an MFS /tmp, add to fstab(5) then mount /tmp md/tmpmfs rw,-s64m,-m02 0 Let me know if the syntax error persists. ~BAS On Tue, 2007-03-27 at 16:17 +0200, Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
Thanks, but the point is I have no MFS module loaded and i cannot compile the kernel... this is useless. On 3/27/07, Brian A. Seklecki [EMAIL PROTECTED] wrote: Just run an MFS /tmp, add to fstab(5) then mount /tmp md/tmpmfs rw,-s64m,-m02 0 Let me know if the syntax error persists. ~BAS On Tue, 2007-03-27 at 16:17 +0200, Michele Endrici wrote: Hi, can anyone help me find a solution to a make problem?? I'm trying to build a kernel for FreeBSD 6.2 with a new driver but the make fails. I tryed in both the old and new school ways but it didn't work anyway. Here is the error i get: /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zlib created for /usr/src/sys/modules/zlib -- stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_gram.y /tmp: write failed, filesystem is full yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c aicasm_gram.c aicasm_gram.c: In function `yyparse': aicasm_gram.c:2146: error: `initialize_symb' undeclared (first use in this function) aicasm_gram.c:2146: error: (Each undeclared identifier is reported only once aicasm_gram.c:2146: error: for each function it appears in.) aicasm_gram.c:2146: error: syntax error before '}' token aicasm_gram.c:2201: error: syntax error at end of input *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. First of all it tells me /tmp filesystem is full. I run df -h and it's quite full. Hence, I've created a symbolic link to another folder to gain more space ln -s /tmp /var/tmp_fake but i still get the same error. Any suggestion?? Michele -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
On Tue, 2007-03-27 at 17:42 +0200, Michele Endrici wrote: build a kernel for FreeBSD 6.2 with a new driver but the make fails build a kernel for FreeBSD 6.2 with a new driver but the make fails What did you do just pull a new version of the files into your 6.2 tree? from -current? from RELENG_6 branch? Did you get a patch known to work? This isn't Debian :} -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /tmp write failed, filesystem is full
No, i'm working on a driver prototype for my master thesis degree. I've simply got this driver that is known working on 6.1 and changed some code. Put the driver files in the /usr/src/sys/dev/drive_dir, added the line dev/drive_dir/drive_name.c to files.i386, than build it statically into kernel with make depend, make, make install. First time it worked than no more. I know i can do a kernel plug-in instead this static kernel module but I need to solve this problem anyway. On 3/27/07, Brian A. Seklecki [EMAIL PROTECTED] wrote: On Tue, 2007-03-27 at 17:42 +0200, Michele Endrici wrote: build a kernel for FreeBSD 6.2 with a new driver but the make fails build a kernel for FreeBSD 6.2 with a new driver but the make fails What did you do just pull a new version of the files into your 6.2 tree? from -current? from RELENG_6 branch? Did you get a patch known to work? This isn't Debian :} -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. -- Michele Endrici Via carraia 4 - Don - TN tel: 348-7295670 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/: write failed, filesystem is full
Hello, I have a problem with the filesystem. I am always getting those /: write failed, filesystem is full errors. If I have a look on df the root has 109% Capacity. How could that be? I had a file in /root with 3.3G that I have now deleted but with no success. The df output is as before. I am using Raid1(Mirror) with two 80Gig ST380011A/3.04 HDs. df -h FilesystemSize Used Avail Capacity Mounted on /dev/ar0s1a 4.9G 4.9G -400.7M 109%/ devfs 1.0K 1.0K 0B 100%/dev /dev/ar0s1d21G 2.5G16G13%/usr /dev/ar0s1e 3.9G 555M 3.1G15%/var /dev/ar0s1f43G 885M39G 2%/www my disk usage: du -hd1 1.5K./dev 2.5G./usr 555M./var 885M./www 2.4M./stand 1.5M./etc 2.0K./cdrom 2.0K./dist 7.3M./bin 18M./boot 2.0K./mnt 2.0K./proc 18M./root 21M./sbin 24K./tmp 76K./cgb 4.0G. The du output does not agree with the df output. Where are the 4.9Gig of / ? What can I do? Somebody had this problem before? Thanks, Joachim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, jojo wrote: Hello, I have a problem with the filesystem. I am always getting those /: write failed, filesystem is full errors. If I have a look on df the root has 109% Capacity. How could that be? I had a file in /root with 3.3G that I have now deleted but with no success. The df output is as before. I am using Raid1(Mirror) with two 80Gig ST380011A/3.04 HDs. The filesystem always reserves a bit of space above 100%. Normal users can fill the filesystem up to 100%, and the root user can go to 110% (if I remember orrectly). Hence the 109%. du -hd1 1.5K./dev 2.5G./usr 555M./var 885M./www 2.4M./stand 1.5M./etc 2.0K./cdrom 2.0K./dist 7.3M./bin 18M./boot 2.0K./mnt 2.0K./proc 18M./root 21M./sbin 24K./tmp 76K./cgb 4.0G. The du output does not agree with the df output. Where are the 4.9Gig of / ? What can I do? Somebody had this problem before? As you can see, the contents of /var, /www and /usr are also counted, which are on another file system. You might try du -hx / in order to see only the contents of / and the directories on that file system. Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? Yours, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, jojo wrote: Hello, I have a problem with the filesystem. I am always getting those /: write failed, filesystem is full errors. If I have a look on df the root has 109% Capacity. How could that be? I had a file in /root with 3.3G that I have now deleted but with no success. The df output is as before. I am using Raid1(Mirror) with two 80Gig ST380011A/3.04 HDs. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq /disks.html#DISK-MORE-THAN-FULL Regards, Uli. df -h FilesystemSize Used Avail Capacity Mounted on /dev/ar0s1a 4.9G 4.9G -400.7M 109%/ devfs 1.0K 1.0K 0B 100%/dev /dev/ar0s1d21G 2.5G16G13%/usr /dev/ar0s1e 3.9G 555M 3.1G15%/var /dev/ar0s1f43G 885M39G 2%/www my disk usage: du -hd1 1.5K./dev 2.5G./usr 555M./var 885M./www 2.4M./stand 1.5M./etc 2.0K./cdrom 2.0K./dist 7.3M./bin 18M./boot 2.0K./mnt 2.0K./proc 18M./root 21M./sbin 24K./tmp 76K./cgb 4.0G. The du output does not agree with the df output. Where are the 4.9Gig of / ? What can I do? Somebody had this problem before? Thanks, Joachim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, Jaap Boender wrote: Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? Oh, wait, I read you wrongly. The file from /root has disappeared all right (only 18M in there). The 4.0G you read includes the total of everything below it, such as the /usr and /www and so on. If you only want the / file system, try the -x option, as I said. Sorry, Jaap ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On 10/5/05, P.U.Kruppa [EMAIL PROTECTED] wrote: On Wed, 5 Oct 2005, jojo wrote: Hello, I have a problem with the filesystem. I am always getting those /: write failed, filesystem is full errors. If I have a look on df the root has 109% Capacity. How could that be? I had a file in /root with 3.3G that I have now deleted but with no success. The df output is as before. I am using Raid1(Mirror) with two 80Gig ST380011A/3.04 HDs. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq /disks.html#DISK-MORE-THAN-FULL As well as http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DU-VS-DF i.e. read sections 9.23 and 9.26 of the FAQ. Or just reboot. Crude, and not very informative, but it will fix it. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, Jaap Boender wrote: Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? It was a output file from tcpdump ( /root/test.txt ) Oh, wait, I read you wrongly. The file from /root has disappeared all right (only 18M in there). The 4.0G you read includes the total of everything below it, such as the /usr and /www and so on. If you only want the / file system, try the -x option, as I said. Sorry, Jaap Hi, ok now I did: cd / du -xhcd1 512B./dev 2.0K./usr 2.0K./var 2.0K./www 2.4M./stand 1.5M./etc 2.0K./cdrom 2.0K./dist 7.3M./bin 18M./boot 2.0K./mnt 2.0K./proc 18M./root 21M./sbin 24K./tmp 76K./cgb 68M. 68Mtotal Anyway - I can´t see the 4,9Gig. df -h FilesystemSize Used Avail Capacity Mounted on /dev/ar0s1a 4.9G 4.9G -400.7M 109%/ devfs 1.0K 1.0K 0B 100%/dev /dev/ar0s1d21G 2.5G16G13%/usr /dev/ar0s1e 3.9G 555M 3.1G15%/var /dev/ar0s1f43G 885M39G 2%/www Thanks, Joachim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On 10/5/05, jojo [EMAIL PROTECTED] wrote: On Wed, 5 Oct 2005, Jaap Boender wrote: Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? It was a output file from tcpdump ( /root/test.txt ) Something still has the file open. Even though the file no longer has a directory entry, its disk space can't be released until nothing has it open. Either tcpdump or some program you were using to view the file must still have it open. If you get tired of looking for the culprit, a reboot will guarantee it gets closed. If you want to solve the mystery, fstat should help. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
Hi all, ok, the problem is solved. tcpdump was still open and used the file as Bob already said. Sorry for my stupidity :) Thanks to all, Joachim Something still has the file open. Even though the file no longer has a directory entry, its disk space can't be released until nothing has it open. Either tcpdump or some program you were using to view the file must still have it open. If you get tired of looking for the culprit, a reboot will guarantee it gets closed. If you want to solve the mystery, fstat should help. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NTFS filesystem in hard, but: @/:write failed, filesystem is full@
Hi! Does anybody explain me why i can't install FreeBSD on new HDD? I have just NTFS hard drive formatted, but when i start freebsd install i see next: Probing devices (this can take a while) And next: /:write falied, filesystem is full What is it? What I must do next? Thanks. Denis. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
