The math is off because some space is reserved for UID 0 / root. Read
these two man pages:
~BAS
NEWFS(8) FreeBSD System Manager's Manual NEWFS(8)
NAME
newfs -- construct a new UFS1/UFS2 file system
-m free-space
The percentage of space reserved from normal
Hi all
What's that mean ?
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ad4s1a50763069050 39797015%/
devfs 110 100%/dev
/dev/ad4s1g 78017664 55539220 1623703277%/home
/dev/ad4s1e507630-8960 475980
cc
Subject
Strange df
Hi all
What's that mean ?
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ad4s1a50763069050 39797015%/
devfs 110 100%/dev
/dev/ad4s1g 78017664 55539220 1623703277%/home
/dev/ad4s1e
On Fri, 2007-10-05 at 13:11 +0300, Ivailo Tanusheff wrote:
This seams as a wrong lable info.
Check: bsdlabel /dev/ad4s1
Oh wow, yea, I misread.
That's really scarry -- normally the kernel would panic. I'm very
surprised bsdlabel(8) let you write that to the disk.
Does fsck(8) function? Did
Le 05/10/2007 à 13:11:34+0300, Ivailo Tanusheff a écrit
This seams as a wrong lable info.
Check: bsdlabel /dev/ad4s1
Why you say that ? the /dev/ad4s1e is really mounted on /tmp
This strange thing appear after I make some clean up (rm old.pdf etc...) in
my /tmp
Hi all
What's
Le 05/10/2007 à 12:12:26+0200, Albert Shih a écrit
Hi all
What's that mean ?
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ad4s1a50763069050 39797015%/
devfs 110 100%/dev
/dev/ad4s1g 78017664 55539220 16237032
On Fri, Oct 05, 2007 at 04:24:33PM +0200, Albert Shih wrote:
Le 05/10/2007 à 12:12:26+0200, Albert Shih a écrit
Hi all
What's that mean ?
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ad4s1a50763069050 39797015%/
devfs 1
On Fri, Oct 05, 2007 at 12:12:26PM +0200, Albert Shih wrote:
Hi all
What's that mean ?
What does it look like?
It looks to me like the output of a df(1) command -
specifically 'df -k'
The first line contains labels that explain what is in each column.
The file system or partition device
Hi guys,
In the daily run output, the disk status always starts to look a bit
strange on one of my machines. I think this starts after about three
weeks of uptime.
It never seems to cause any serious problems, but today I decided to
find out why this happens. :) I couldn't find any answers
