From: Jim Salter <jim@jrs-s.net>
To: Marcus Sundman <sundman@iki.fi>, linux-btrfs@vger.kernel.org
Subject: Re: No space left on device (again)
Date: Tue, 25 Feb 2014 13:05:51 -0500 [thread overview]
Message-ID: <530CDB7F.9020807@jrs-s.net> (raw)
In-Reply-To: <530CC9B0.1080703@iki.fi>
370GB of 410GB used isn't really "fine", it's over 90% usage.
That said, I'd be interested to know why btrfs fi show /dev/sda3 shows
412.54G used, but btrfs fi df /home shows 379G used...
On 02/25/2014 11:49 AM, Marcus Sundman wrote:
> Hi
>
> I get "No space left on device" and it is unclear why:
>
>> # df -h|grep sda3
>> /dev/sda3 413G 368G 45G 90% /home
>> # btrfs filesystem show /dev/sda3
>> Label: 'home' uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
>> Total devices 1 FS bytes used 371.11GB
>> devid 1 size 412.54GB used 412.54GB path /dev/sda3
>>
>> Btrfs v0.20-rc1
>> # btrfs filesystem df /home
>> Data: total=410.52GB, used=369.61GB
>> System: total=4.00MB, used=64.00KB
>> Metadata: total=2.01GB, used=1.50GB
>> #
>
> So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit
> low. Is that it? If so, can I do something about it? Or should I look
> somewhere else?
>
> I really wish I could get a warning before running out of disk space,
> instead of everything breaking suddenly when there seems to be lots
> and lots of space left.
>
> - Marcus
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-25 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 16:49 No space left on device (again) Marcus Sundman
2014-02-25 18:05 ` Jim Salter [this message]
2014-02-25 19:59 ` Marcus Sundman
2014-02-25 20:19 ` Hugo Mills
2014-02-25 20:27 ` Marcus Sundman
2014-02-25 20:30 ` Josef Bacik
2014-02-26 10:38 ` Sander
2014-02-27 0:16 ` Marcus Sundman
2014-02-27 1:17 ` Josef Bacik
2014-02-27 7:48 ` Hugo Mills
2014-02-25 20:30 ` cwillu
2014-02-25 20:40 ` Hugo Mills
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=530CDB7F.9020807@jrs-s.net \
--to=jim@jrs-s.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sundman@iki.fi \
/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