From: Stefan Priebe <s.priebe@profihost.ag>
To: Roman Mamedov <rm@romanrm.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>, clm@fb.com
Subject: Re: kernel 4.1: no space left on device
Date: Sat, 27 Jun 2015 18:10:51 +0200 [thread overview]
Message-ID: <558ECB0B.3060505@profihost.ag> (raw)
In-Reply-To: <20150627205148.284ff359@natsu>
Am 27.06.2015 um 17:51 schrieb Roman Mamedov:
> On Sat, 27 Jun 2015 17:32:04 +0200
> Stefan Priebe <s.priebe@profihost.ag> wrote:
>
>> Hi,
>>
>> while having some big btrfs volumes (44TB + 37TB).
>>
>> I see on a regular basis the "no space left on device" message. I'm only
>> able to "fix" this. By running btrfs balance AND unmounting and
>> remounting the btrfs volume.
>>
>> Is there any way to debug / workaround this one?
>
> You should post your 'df', 'btrfs fi df' and 'btrfs fi show' for both devices.
sorry - here for one server:
[ ~]# btrfs filesystem df /vmbackup/
Data, single: total=7.58TiB, used=7.58TiB
System, DUP: total=8.00MiB, used=1.19MiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=69.00GiB, used=38.25GiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=3.30MiB
[ ~]# btrfs fi show /vmbackup/
Label: none uuid: 0df5ed87-07da-4c15-9a2b-1d0ff6ec208d
Total devices 1 FS bytes used 7.62TiB
devid 1 size 43.66TiB used 7.72TiB path /dev/md50
btrfs-progs v4.0.1
Stefan
next prev parent reply other threads:[~2015-06-27 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 15:32 kernel 4.1: no space left on device Stefan Priebe
2015-06-27 15:45 ` Moby
2015-06-27 15:51 ` Roman Mamedov
2015-06-27 16:10 ` Stefan Priebe [this message]
[not found] ` <CABE5tBY0fbL5tGRnTOB+eMeQxHJRWBWXiwQiEQNHShLPnq0rpw@mail.gmail.com>
2015-06-28 8:56 ` Stefan Priebe
2015-06-28 16:33 ` Chris Murphy
2015-07-18 18:18 ` Stefan Priebe
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=558ECB0B.3060505@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=clm@fb.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 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).