[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
available free disk space on /usr and crash
- Subject: available free disk space on /usr and crash
- From: brooks at one-eyed-alien.net (Brooks Davis)
- Date: Thu Jan 27 09:19:13 2005
On Thu, Jan 27, 2005 at 12:54:03PM +0100, Aron wrote:
> I am tracking FreeBSD 5.3 stable and somehow got to a state where df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/ad0s1a 253678 53606 179778 23% /
> devfs 1 1 0 100% /dev
> /dev/ad0s1e 253678 88 233296 0% /tmp
> /dev/ad0s1f 4261038 3989064 -68908 102% /usr
> /dev/ad0s1g 13999734 11318544 1561212 88% /usr/home
> /dev/ad2s1 153844706 133929864 7607266 95% /usr/srv/disk1
> /dev/ad1s1d 109093546 39760220 60605844 40% /usr/srv/disk2
> /dev/ad0s1d 253678 53858 179526 23% /var
> I don't have the slightest idea how this happened, but thought someone
> should be notified. I didn't really do anything with the /usr partition
> beside of cvsuping and rebuilding world and the ports from time to time.
> The freebsd machine is used as a server and runs a vsftpd, samba,
> apache2 and a subversion server. Deleting a few files brought the free
> disk space on /usr back to a positive number.
/usr looks perfectly normal if full. This is just basic UNIX operation.
A certain portion of the disk (set at newfs time) is reserved for use by
the root user (performance may degrade significantly if this space is
used). Avail and Capacity are computed relative to the non-reserved
> I also managed to lock up FreeBSD (just before I noticed the free disk
> space problem). I uploaded a larger (well, 31MB) encrypted (via PGP)
> file to a samba network directory from my WinXP client machine (freebsd
> runs samba 3.0.10 just for the case it mattered, the samba directory is
> located on the /usr/home partition). I ran PGP (on my windows machine)
> and pointed it to the encrypted file located on the network. After
> having decrypted about 30% of the file FreeBSD kind of locked up, or at
> least it stopped responding (I couldn't even ping the freeBSD machine
> anymore). Pressing the power-off button seemed to force FreeBSD shutdown
> properly, so I guess the computer wasn't as dead as I had thought.
You'll need to read the the FreeBSD Developers Handbook section on
kernel debugging and obtain a crash dump from your machine.
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-bugs/attachments/20050127/30a7d9d3/attachment.bin