Date: Mon, 24 Jul 2006 16:48:32 +0100 From: Feargal Reilly <feargal@helgrim.com> To: freebsd-stable@freebsd.org Subject: Re: filesystem full error with inumber Message-ID: <20060724164832.11683f08@mablung.edhellond.fbi.ie> In-Reply-To: <200607241514.k6OFERos052696@lurza.secnetix.de> References: <20060721140005.5365e4b7@mablung.edhellond.fbi.ie> <200607241514.k6OFERos052696@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_8mWkG7M.EDc2L7O8RQHTbS= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 24 Jul 2006 17:14:27 +0200 (CEST) Oliver Fromme <olli@lurza.secnetix.de> wrote: > Nobody else has answered so far, so I try to give it a shot ... >=20 > 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 inodes. > 3. The file system is running out of non-fragmented blocks. >=20 > The third case can only happen on extremely fragmented > file systems which happens very rarely, but maybe it's > a possible cause of your problem. I rebooted that server, and df then reported that disk at 108%, so it appears that df was reporting incorrect figures prior to the reboot. Having cleaned up, it appears by my best calculations to be showing correct figures now. > > kern.maxfiles: 20000 > > kern.openfiles: 3582 >=20 > Those have nothing to do with "filesystem full". >=20 Yeah, that's what I figured. > > 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) says: [...] > > Reading this makes me think that when this server was > > installed, the block size was dropped from the 16K default > > to 8K for performance reasons, but the fragment size was > > not modified accordingly. > >=20 > > Would this be the root of my problem? >=20 > I think a bsize/fsize ratio of 4/1 _should_ work, but it's > not widely used, so there might be bugs hidden somewhere. >=20 Such as df not reporting the actual data usage, which is now my best working theory. I don't know what df bases it's figures on, perhaps it either slowly got out of sync, or more likely, got things wrong once the disk filled up. I'll monitor it to see if this happens again, but hopefully won't keep that configuration around for too much longer anyway. Thanks, -fr. --=20 Feargal Reilly. PGP Key: 0x847DE4C8 (expires: 2006-11-30) Web: http://www.helgrim.com/ | ICQ: 109837009 | YIM: ectoraige Visit http://ie.bsd.net/ - BSDs presence in Ireland --Sig_8mWkG7M.EDc2L7O8RQHTbS= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFExOvQHfl+zYR95MgRAkxgAJ9v8yja+81hyTw95wGnx6Kex2gSWQCfa7vG s8AXxUMOrUdMwZY0msAQqQY= =rgCR -----END PGP SIGNATURE----- --Sig_8mWkG7M.EDc2L7O8RQHTbS=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060724164832.11683f08>