linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert White <rwhite@pobox.com>
To: "sys.syphus" <syssyphus@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: out of space warning?
Date: Wed, 10 Dec 2014 17:29:20 -0800	[thread overview]
Message-ID: <5488F370.2060604@pobox.com> (raw)
In-Reply-To: <CAAe=sHXGpiZN5hKmzv1ynY8x=rH9tMvx86HZP2veLRpAFJN+wg@mail.gmail.com>

On 12/10/2014 02:54 PM, sys.syphus wrote:
> I would like to avoid running out of space. is there a way to know
> that I am getting close? i'd like to make a script that runs as part
> of my bash prompt and lets me know when i am getting close. i know
> there are several ways you can run out of space and I'd like to avoid
> all of them.

Don't do that either. 8-)

(1) you'll grow to hate it.

(2) You know when you are doing things that take a lot of storage. You 
instinct for system fullness is already part of your brain-meat.

(3) The system isn't going to explode if it runs out of disk space. (old 
UNIX systems used to halt with system errors because running out of 
space prevented pipelines from being created, but that's ancient history).

(4) The only _real_ way to run out of space is to be a data hoarder, and 
no script in the world is going to help you if that's the case. Ha Ha....

You don't check your car's gas tank every time you put your foot on the 
brake, you don't want to check your free space every time your system 
finishes every tiny command you type.

Scripts like this are possible in bash, but consider that every "ls" or 
even just enter you type would be followed by a "df" and a "grep" or 
whatever in whatever window you are using at the time. etc.

IF you think you are going to run out of space, and you are using _any_ 
kind of window system, then start a system manager display for a while 
until you get the feel for how not out of space you really are.

Nothing gets ignored faster than a text element that essentially never 
changes, and once you get in the habbit of ignoring the text you won't 
notice when it actually has something to say.


  reply	other threads:[~2014-12-11  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 22:54 out of space warning? sys.syphus
2014-12-11  1:29 ` Robert White [this message]
2014-12-11  2:46   ` Qu Wenruo
2014-12-11  9:01   ` Erkki Seppala
2014-12-11  9:29     ` Robert White
2014-12-11  8:16 ` Duncan

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=5488F370.2060604@pobox.com \
    --to=rwhite@pobox.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=syssyphus@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).