From: Gerard Saraber <gsaraber@rarcoa.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: No space left on device when doing "mkdir"
Date: Thu, 27 Apr 2017 10:18:22 -0500 [thread overview]
Message-ID: <CAPsdh33mN-QuL+-Z5UmO7Tmn4rEQs7_6X3a0D2T0APYkm5YR2A@mail.gmail.com> (raw)
In-Reply-To: <20170427190751.2dc0e7ac@natsu>
no snapshots and no qgroups, just a straight up large volume.
shrapnel gerard-store # btrfs fi df /home/exports
Data, RAID1: total=20.93TiB, used=20.86TiB
System, RAID1: total=32.00MiB, used=3.73MiB
Metadata, RAID1: total=79.00GiB, used=61.10GiB
GlobalReserve, single: total=512.00MiB, used=544.00KiB
shrapnel gerard-store # btrfs filesystem usage /home/exports
Overall:
Device size: 69.13TiB
Device allocated: 42.01TiB
Device unallocated: 27.13TiB
Device missing: 0.00B
Used: 41.84TiB
Free (estimated): 13.63TiB (min: 13.63TiB)
Data ratio: 2.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 1.52MiB)
On Thu, Apr 27, 2017 at 9:07 AM, Roman Mamedov <rm@romanrm.net> wrote:
> On Thu, 27 Apr 2017 08:52:30 -0500
> Gerard Saraber <gsaraber@rarcoa.com> wrote:
>
>> I could just reboot the system and be fine for a week or so, but is
>> there any way to diagnose this?
>
> `btrfs fi df` for a start.
>
> Also obligatory questions: do you have a lot of snapshots, and do you use
> qgroups?
>
> --
> With respect,
> Roman
next prev parent reply other threads:[~2017-04-27 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 13:52 No space left on device when doing "mkdir" Gerard Saraber
2017-04-27 14:07 ` Roman Mamedov
2017-04-27 15:18 ` Gerard Saraber [this message]
2017-04-27 16:46 ` Gerard Saraber
2017-04-27 23:35 ` Chris Murphy
2017-04-28 13:56 ` Gerard Saraber
2017-05-01 19:12 ` Gerard Saraber
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=CAPsdh33mN-QuL+-Z5UmO7Tmn4rEQs7_6X3a0D2T0APYkm5YR2A@mail.gmail.com \
--to=gsaraber@rarcoa.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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.