From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeing up disk space problem!!
Date: Wed, 29 Feb 2012 06:22:56 +0000 [thread overview]
Message-ID: <20120229062256.7ebe60a6@digimed.co.uk> (raw)
In-Reply-To: <20120229020541.405ab461@weird.wonkology.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On Wed, 29 Feb 2012 02:05:41 +0100, Alex Schuster wrote:
> > But if you set m > 0, the filesystem will become full sooner, so
> > fragmentation will begin sooner (for non-root processes).
>
> Uh, really? I wouldn't think so. With m > 0, there is much space left,
> in large contiguous chunks, even though the user cannot use it all. But
> there should be no difference between writing files in terms of
> fragmentation. The reserved stuff acts just like a quota, at least
> that's what I always thought.
Yeah, that makes sense, so why should the reserved setting affect
fragmentation at all, unless you write so much data that the filesystem
would be full with a larger m? In that case, I'd prefer fragmentation to
a failed write.
--
Neil Bothwick
Don't just do something, sit there!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-29 6:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:37 [gentoo-user] Freeing up disk space problem!! trevor donahue
2012-02-28 11:52 ` Alan McKinnon
2012-02-28 13:37 ` William Kenworthy
2012-02-28 11:57 ` Mick
2012-02-28 11:59 ` [gentoo-user] " Nikos Chantziaras
2012-02-28 12:24 ` [gentoo-user] " YoYo Siska
2012-02-28 12:50 ` trevor donahue
2012-02-28 13:25 ` Neil Bothwick
2012-02-28 13:01 ` Alex Schuster
2012-02-28 13:27 ` Neil Bothwick
2012-02-28 23:25 ` Alex Schuster
2012-02-29 0:32 ` Neil Bothwick
2012-02-29 1:05 ` Alex Schuster
2012-02-29 6:22 ` Neil Bothwick [this message]
2012-02-29 9:29 ` Alan McKinnon
2012-02-29 9:57 ` Neil Bothwick
2012-02-29 10:40 ` Alan McKinnon
2012-02-29 11:08 ` Neil Bothwick
2012-02-29 12:11 ` Alan McKinnon
2012-03-01 0:59 ` Frank Steinmetzger
2012-03-01 9:54 ` Neil Bothwick
2012-02-29 23:59 ` [gentoo-user] " walt
2012-03-01 0:43 ` Pandu Poluan
2012-02-29 0:48 ` [gentoo-user] " Dale
2012-02-29 1:01 ` Alex Schuster
2012-02-29 2:38 ` Dale
2012-02-29 6:17 ` Neil Bothwick
2012-02-29 7:10 ` Dale
2012-02-29 7:49 ` J. Roeleveld
2012-02-29 9:23 ` Alan McKinnon
2012-03-01 1:09 ` Frank Steinmetzger
2012-03-01 8:26 ` Alan McKinnon
2012-02-29 9:53 ` Neil Bothwick
2012-02-29 9:19 ` Alan McKinnon
2012-02-29 14:44 ` Dale
2012-02-29 7:43 ` J. Roeleveld
2012-02-29 13:06 ` Daddy
2012-02-29 14:44 ` Dale
2012-02-28 16:14 ` James Broadhead
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120229062256.7ebe60a6@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox