Derek Ragona wrote:
I would reboot and run fsck in single user mode. The reboot will
clear any old open files that may be causing the drive full problem.
-Derek
At 11:59 AM 4/3/2007, Sean Murphy wrote:
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h
I am getting these errors on my var filesystem but df -h shows there is
plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M854M 6%/
devfs1.0K1.0K 0B 100%
Run fsck on /var
also check that /var doesn't exist elseware like from a symbolic link.
-Derek
At 11:18 AM 4/3/2007, Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there is
plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
On Apr 3, 2007, at 12:18 PM, Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows
there is plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M854M 6%
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there
is plenty of space available.
Check df -i as you may have run out of inodes rather than out of file space.
--Alex
___
freebsd-questions@freebsd.org mailing
On Tue, Apr 03, 2007 at 09:18:29AM -0700, Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there is
plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M
lsof is your friend
Alex Zbyslaw wrote:
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there
is plenty of space available.
Check df -i as you may have run out of inodes rather than out of file
space.
--Alex
Alex Zbyslaw wrote:
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there
is plenty of space available.
Check df -i as you may have run out of inodes rather than out of file
space.
Also, try working with fstat(1) to see if the offending superbig file
is
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there
is plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M854M 6%/
devfs1.0K
On Tuesday 03 April 2007 09:18:29 Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there is
plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M854M
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there is
plenty of space available.
I am running FreeBSD 5.4
muse2# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/amrd0s1a989M 56M854M 6%/
devfs1.0K
Noah wrote:
Alex Zbyslaw wrote:
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there
is plenty of space available.
Check df -i as you may have run out of inodes rather than out of file
space.
lsof is your friend
First of all, please don't top-post.
Sean Murphy wrote:
Check df -i as you may have run out of inodes rather than out of file
space.
Looks as though I have plenty of inodes
muse2# df -i
Filesystem1K-blocksUsed Avail Capacity iusedifree
%iused Mounted on
/dev/amrd0s1a 1012974 57694874244 6%1520
--On Tuesday, April 03, 2007 18:12:09 +0100 Alex Zbyslaw
[EMAIL PROTECTED] wrote:
The available disk space start at 4554194, drops to 4451714 when the
file is created, and *remains like that* until the process holding the
file open exits, thus freeing the last reference and allowing the blocks
I would reboot and run fsck in single user mode. The reboot will clear any
old open files that may be causing the drive full problem.
-Derek
At 11:59 AM 4/3/2007, Sean Murphy wrote:
Sean Murphy wrote:
I am getting these errors on my var filesystem but df -h shows there is
plenty of
15 matches
Mail list logo