From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S2uOR-0000Pa-7I for garchives@archives.gentoo.org; Thu, 01 Mar 2012 01:01:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5D092E0912; Thu, 1 Mar 2012 01:01:04 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pigeon.gentoo.org (Postfix) with SMTP id 32514E07BC for ; Thu, 1 Mar 2012 00:59:41 +0000 (UTC) Received: (qmail invoked by alias); 01 Mar 2012 00:59:41 -0000 Received: from wl-l3-93.rz.tu-ilmenau.de (EHLO localhost) [141.24.17.93] by mail.gmx.net (mp017) with SMTP; 01 Mar 2012 01:59:41 +0100 X-Authenticated: #4040096 X-Provags-ID: V01U2FsdGVkX1+XJlNMwMOXtj+ZRKDjK7Y3Ag+fqygik5gd+5tgm/ y/3SoP8HCRPFdF Date: Thu, 1 Mar 2012 01:59:41 +0100 From: Frank Steinmetzger To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Freeing up disk space problem!! Message-ID: <20120301005941.GA6178@eisen.lan> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20120228140150.2b35b864@weird.wonkology.org> <20120228132712.6df1ca07@digimed.co.uk> <20120229002500.6d2ab8a9@weird.wonkology.org> <20120229112945.73867e57@khamul.example.com> <20120229095719.59fe466d@digimed.co.uk> <20120229124033.071ed7d6@khamul.example.com> <20120229110849.5bec507c@digimed.co.uk> <20120229141141.7c047149@khamul.example.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20120229141141.7c047149@khamul.example.com> User-Agent: Mutt 1.5.21 (2010-09-15, Gentoo 1.5.21-r1) X-Y-GMX-Trusted: 0 X-Archives-Salt: 2db2a621-6d4a-4482-99e1-166ce7cfb2d7 X-Archives-Hash: 33b10d68c26541a27542b840293cd067 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 29, 2012 at 02:11:41PM +0200, Alan McKinnon wrote: > > I've never failed to fix that by deleting a file as the user that > > created it, usually the partial file that caused the problem, but I > > can see why you may want to keep a small amount reserved for that. > >=20 > > However, I still don't get the "-m 0 increases fragmentation" thing. > >=20 > >=20 >=20 > Yeah, that sounds like an old wives tale urban myth to me too >=20 > I'll be wanting to be seeing the output of real diagnostic programs All that does, as far as I understand it, is to fool $user into having less space available. So if the partition only has as much space left as is reserved for root, he just can't write anymore. It just means that before the drive gets physically full (which means that files will fragment more), it will get logically full earlier. This is why there can be expected less fragmentation under extreme circumstances (i.e. = an almost full FS). --=20 Gru=C3=9F | Greetings | Qapla' I forbid any use of my email addresses with Facebook services. When the going gets tough, the tough get going. =2E.. and so do I. =E2=80=93 Alf --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk9OyfwACgkQGafpl66MV0zTVgCfT+jfJgDZo26NcGXqiO/qZj+9 NPkAoI6/5vGl36HH8H3wDjTNFI+4mVDa =gK6X -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--