From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: out of space warning?
Date: Thu, 11 Dec 2014 08:16:28 +0000 (UTC) [thread overview]
Message-ID: <pan$6aed4$da742710$2d9d1dc2$995131a9@cox.net> (raw)
In-Reply-To: CAAe=sHXGpiZN5hKmzv1ynY8x=rH9tMvx86HZP2veLRpAFJN+wg@mail.gmail.com
sys.syphus posted on Wed, 10 Dec 2014 16:54:07 -0600 as excerpted:
> 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.
With the concerns about your bash prompt registered...
btrfs filesystem show
... is a good choice.
If you have multiple filesystems you can point show at a device/
mountpoint/label/UUID to get the output for just the one.
You'll want to pay particular attention to the individual device lines.
Of course you can grep/sed/otherwise-process that down to a single line
if desired.
If btrfs filesystem show says it's close to out of room, run btrfs
filesystem df for more info. There's lots of information on the wiki and
in various threads here about interpreting the information these commands
output (it takes both commands to get a good picture, but show is good
for brief summary, provided you know to look at the device lines not the
overall total line), and what to do when necessary to return some balance
to the situation.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-12-11 8:16 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
2014-12-11 9:29 ` Robert White
2014-12-11 8:16 ` Duncan [this message]
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='pan$6aed4$da742710$2d9d1dc2$995131a9@cox.net' \
--to=1i5t5.duncan@cox.net \
--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.