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
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
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
, 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
- 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
- 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
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
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
/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
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
;
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
/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
/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
/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
/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
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
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
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
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
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
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
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
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
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
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
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.
26 matches
Mail list logo
