DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 1st June 2008
nathang nathang is offline
New User
 
Join Date: Jun 2008
Posts: 4
Thanked 0 Times in 0 Posts
Default Incorrect df results (not -h, not a FAQ)

All,

I've been encountering some strange problems with one of our servers. The following is the df and mount output:

Code:
Filesystem    1K-blocks      Used    Avail Capacity  iused   ifree %iused  Mounted on
/dev/mfid0s1a 137729560 106243486 20467710    84% 11261804 6543506   63%   /
devfs                 1         1        0   100%        0       0  100%   /dev
procfs                4         4        0   100%        1       0  100%   /proc


/dev/mfid0s1a on / (ufs, NFS exported, local, soft-updates)
devfs on /dev (devfs, local)
procfs on /proc (procfs, local)
Unfortunately, no data can be written to the disk (well I'm glossing over a minor detail). A reboot did not resolve the problem. Any ideas would be appreciated. Note: this is a dell using the MFI driver. And: FreeBSD 6.3-PRERELEASE amd64

Thanks in advance.
Reply With Quote
  #2   (View Single Post)  
Old 1st June 2008
corey_james corey_james is offline
Uber Geek
 
Join Date: Apr 2008
Location: Brisbane, Australia
Posts: 238
Thanked 4 Times in 10 Posts
Default

rebooting unix systems never fixes anything ...

can you post at least a log or an error msg ?
__________________
"No, that's wrong, Cartman. But don't worry, there are no stupid answers, just stupid people." -- Mr. Garrison

Forum Netiquette
Reply With Quote
  #3   (View Single Post)  
Old 1st June 2008
nathang nathang is offline
New User
 
Join Date: Jun 2008
Posts: 4
Thanked 0 Times in 0 Posts
Default

If you were talking about AIX, then I might agree . . . The error message is very simple:

Code:
[user@host]$ cat /dev/zero > zero.bin

/: write failed, filesystem is full
cat: stdout: No space left on device
-=[~]=- -=[Sun Jun 01]=- -=[07:13:13]=-
[user@host]$ ls -l zero.bin 
-rw-r--r--  1 user  user  4096 Jun  1 07:13 zero.bin
-=[~]=- -=[Sun Jun 01]=- -=[07:13:28]=-
[user@host]$
Reply With Quote
  #4   (View Single Post)  
Old 1st June 2008
robbak's Avatar
robbak robbak is offline
Real Name: Robert Backhaus
VPN Cryptographer
 
Join Date: May 2008
Location: North Queensland, Australia
Posts: 366
Thanked 40 Times in 39 Posts
Default

Next step is to check in /var/log/messages and /var/log/all.log (and any others that look suspicious) for any error messages.

I'd say that there is some condition in the raid array that is being posted (eventually) as a 'disk full' error. The system log should give you some ideas.
__________________
The only dumb question is a question not asked.
The only dumb answer is an answer not given.
Reply With Quote
  #5   (View Single Post)  
Old 1st June 2008
TerryP's Avatar
TerryP TerryP is offline
Arp Constable
 
Join Date: May 2008
Location: USofA
Posts: 1,547
Thanked 112 Times in 104 Posts
Default

Depending on what the real disk size is and assuming it is full, it might be failing to write because some disk space is held back:

Quote:
Originally Posted by tunefs
-m minfree
Specify the percentage of space held back from normal users; the
minimum free space threshold. The default value used is 8%.
Note that lowering the threshold can adversely affect perfor-
mance:

+o Settings of 5% and less force space optimization to always be
used which will greatly increase the overhead for file
writes.

+o The file system's ability to avoid fragmentation will be
reduced when the total free space, including the reserve,
drops below 15%. As free space approaches zero, throughput
can degrade by up to a factor of three over the performance
obtained at a 10% threshold.

If the value is raised above the current usage level, users will
be unable to allocate files until enough files have been deleted
to get under the higher threshold.

Depending on what servers purpose, I'd look at the disk contents as well as the logs.


I remember *twice* having a few hundred megs of core-dumps from php4 causing trouble on a RHEL machine, whose host tried to charge us for more disk space :-)

If it's a mails server, I'd trust people have tight quotas that fit on disk even if everyones full hehe.
__________________
My Journal

Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.
Reply With Quote
  #6   (View Single Post)  
Old 8th June 2008
nathang nathang is offline
New User
 
Join Date: Jun 2008
Posts: 4
Thanked 0 Times in 0 Posts
Default Problem Solved (well, not solved, but understood at least)

The answer is, as usual, quit simple: 22.8% fragmentation on a UFS2 file-system with a 2K fragment-size. Fixing it, however, is another problem. Sometimes I pine for DOS and tiny hard drives. And thanks for the tunefs tip, it led me down the right path.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
STORAGE: benchmarks results (diskinfo) vermaden FreeBSD General 53 28th November 2010 06:06 PM
Successfully booting NetBSD Live on a Sony Vaio PCG-GRZ530 with limited results Mr-Biscuit NetBSD General 6 26th May 2009 11:47 AM
question about "sockstat -4" results bgobs FreeBSD General 3 10th June 2008 09:57 AM


All times are GMT. The time now is 10:28 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick