On Wed, 26 Jul 2006 13:07:19 -0400
Sven Willenberger [EMAIL PROTECTED] wrote:
Feargal Reilly presumably uttered the following on 07/24/06
11:48:
Looking again at dumpfs, it appears to say that this is
formatted with a block size of 8K, and a fragment size of
2K, but tuning(7)
Sven Willenberger wrote:
This was an upgrade from a 5.x system (UFS2); a full fsck did in fact fix the
problem (for now).
Because of past experience I recommend that you disable
background fsck (it has a switch in /etc/rc.conf). There
are failure scenarios with background fsck that can lead
Feargal Reilly [EMAIL PROTECTED] wrote:
BTW, anybody know what the best method be for double-checking
df's figures would be? du?
No, du(1) only sees files that have links (i.e. directory
entries). It doesn't see deleted files that occupy space
as long as processes still have them open, which
Feargal Reilly presumably uttered the following on 07/24/06 11:48:
On Mon, 24 Jul 2006 17:14:27 +0200 (CEST)
Oliver Fromme [EMAIL PROTECTED] wrote:
Nobody else has answered so far, so I try to give it a shot ...
The filesystem full error can happen in three cases:
1. The file system is
On Wed, 2006-Jul-26 13:07:19 -0400, Sven Willenberger wrote:
One of my machines that I recently upgraded to 6.1 (6.1-RELEASE-p3) is also
exhibiting df reporting wrong data usage numbers.
What did you upgrade from?
Is this UFS1 or UFS2?
Does a full fsck fix the problem?
--
Peter Jeremy
Peter Jeremy presumably uttered the following on 07/26/06 15:00:
On Wed, 2006-Jul-26 13:07:19 -0400, Sven Willenberger wrote:
One of my machines that I recently upgraded to 6.1 (6.1-RELEASE-p3) is also
exhibiting df reporting wrong data usage numbers.
What did you upgrade from?
Is this
Sven Willenberger wrote:
Feargal Reilly presumably uttered the following on 07/24/06 11:48:
On Mon, 24 Jul 2006 17:14:27 +0200 (CEST)
Oliver Fromme [EMAIL PROTECTED] wrote:
Nobody else has answered so far, so I try to give it a shot ...
The filesystem full error can happen in
From Julian H. Stacey [EMAIL PROTECTED], Thu, Jul 27, 2006 at 01:45:16AM
+0200:
Negative isnt an example of programming error, just that the system
is now using the last bit only root can use.
for insight try for example
man tunefs
reboot
boot -s
tunefs -m 2
On Mon, 24 Jul 2006 17:14:27 +0200 (CEST)
Oliver Fromme [EMAIL PROTECTED] wrote:
Nobody else has answered so far, so I try to give it a shot ...
The filesystem full error can happen in three cases:
1. The file system is running out of data space.
2. The file system is running out of
The following error is being logged in /var/log/messages on
FreeBSD 5.4:
Jul 21 09:58:44 arwen kernel: pid 615 (postgres), uid 1001
inumber 6166128 on /data0: filesystem full
However, this does not appear to be a case of being out of disk
space, or running out of inodes:
ttyp2$ df -hi
10 matches
Mail list logo
