public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeing up disk space problem!!
Date: Wed, 29 Feb 2012 12:40:33 +0200	[thread overview]
Message-ID: <20120229124033.071ed7d6@khamul.example.com> (raw)
In-Reply-To: <20120229095719.59fe466d@digimed.co.uk>

On Wed, 29 Feb 2012 09:57:19 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Wed, 29 Feb 2012 11:29:45 +0200, Alan McKinnon wrote:
> 
> > It means there's no single sane default anymore. On my servers I set
> > reserved space to 100M or so as that's what I need. I reckon the
> > average person should keep it to somewhat larger than the biggest
> > single file you expect to store on that file system.
> 
> Do you mean the biggest single file you expect root to store on that
> filesystem? Is there any point in reserving space for root on a
> filesystem root does not need to write to, such as /home?
> 
> 

No, I mean the biggest file.

When $LUSER fills up his drive it can be that root is the only user
that can properly mount and access the filesystem. So whatever the
$LUSER was doing that filled up the drive needs to be undone by root,
probably by shuffling stuff around.

There are other cases where root might want some reserved space too,
but fixing full drives is the only case I've ever encountered. 

-- 
Alan McKinnnon
alan.mckinnon@gmail.com




  reply	other threads:[~2012-02-29 10:42 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
2012-02-29  9:29       ` Alan McKinnon
2012-02-29  9:57         ` Neil Bothwick
2012-02-29 10:40           ` Alan McKinnon [this message]
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=20120229124033.071ed7d6@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --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