From owner-freebsd-stable@FreeBSD.ORG Mon Jul 6 20:34:34 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38BDE1065672 for ; Mon, 6 Jul 2009 20:34:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0318FC15 for ; Mon, 6 Jul 2009 20:34:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n66KYSFc045582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Jul 2009 23:34:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n66KYSEV000634; Mon, 6 Jul 2009 23:34:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n66KYRbL000633; Mon, 6 Jul 2009 23:34:27 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 6 Jul 2009 23:34:27 +0300 From: Kostik Belousov To: "Marat N.Afanasyev" Message-ID: <20090706203427.GZ2884@deviant.kiev.zoral.com.ua> References: <4A50E947.9020608@ksu.ru> <4A523518.7050008@gmx.de> <4A523849.1070001@ksu.ru> <20090706193653.GU2884@deviant.kiev.zoral.com.ua> <4A525B72.1010808@ksu.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="D0q9PqIqvBFeK6vt" Content-Disposition: inline In-Reply-To: <4A525B72.1010808@ksu.ru> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Ralf Folkerts , FreeBSD-STABLE Mailing List Subject: Re: bug in ufs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2009 20:34:34 -0000 --D0q9PqIqvBFeK6vt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 07, 2009 at 12:15:46AM +0400, Marat N.Afanasyev wrote: > Kostik Belousov wrote: > >On Mon, Jul 06, 2009 at 09:45:45PM +0400, Marat N.Afanasyev wrote: > >>i have a huge amount of small files on the source systems, as you can= =20 > >>see they have about 20 million files and almost each of them is jpeg or= =20 > >>gif. afaik, there are no sparse files at all. > >> > >>i still cannot figure out what is it: a free space leak in ufs2+su or= =20 > >>bug in statfs(3), that is used in df, or something else. > > > >My guess that it is due to fragmentation. > >As an experiment, try to create 1-byte file. Does it work on the filesys= tem > >in described state ? >=20 > I can create small files, as many as i have patience, maximum size of=20 > such "small file" is 14336, so. it seems that if file is no greater than= =20 > (block_size-2048) it can be created. larger file cannot be created. >=20 > imho, fragmentation on filesystem should be very low, there were no=20 > deletions on it, just creations. The fragmentation on UFS usually means using fragments for the file tails, not having file sequential blocks allocated in the non-sequential disk blocks. You experiment confirms my hypothesis. --D0q9PqIqvBFeK6vt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkpSX9MACgkQC3+MBN1Mb4jgygCeMmOgxVzrTPkVoxCnKl+sjtVV TogAnj27rBmc12PpsGwfcvZiIuPWo9iH =9SPE -----END PGP SIGNATURE----- --D0q9PqIqvBFeK6vt--