All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erkki Seppala <flux-btrfs@inside.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: out of space warning?
Date: Thu, 11 Dec 2014 11:01:33 +0200	[thread overview]
Message-ID: <m49iohiblw2.fsf@coffee.modeemi.fi> (raw)
In-Reply-To: 5488F370.2060604@pobox.com

Robert White <rwhite@pobox.com> writes:

> 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.

Well, actually my car makes a bling every 10 km once it reaches <=80 km
range, and I don't mind it at all ;-).

As an actual answer, there are monitoring systems that do this, such as
Icinga (fork of Nagios). In fact, I just recently had the same problem -
starting a big download might eat up the space and thus terminate the
download prematurely although I was in position for hours to make up
more space, so I installed Icinga. Haven't yet configured yet, though,
so cannot say if it's going to help me :-).

A practical alternative: one could write a script that outputs only the
amount of free space in a device and add that number to your prompt;
possibly to your RPROMPT as to now take too much space from your command
line. Idea extensible to displaying only space from volumes with space
less than a critical amount etc.

-- 
  _____________________________________________________________________
     / __// /__ ____  __               http://www.modeemi.fi/~flux/\   \
    / /_ / // // /\ \/ /                                            \  /
   /_/  /_/ \___/ /_/\_\@modeemi.fi                                  \/


  parent reply	other threads:[~2014-12-11  9:01 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
2014-12-11  2:46   ` Qu Wenruo
2014-12-11  9:01   ` Erkki Seppala [this message]
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=m49iohiblw2.fsf@coffee.modeemi.fi \
    --to=flux-btrfs@inside.org \
    --cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.