From: Stefan Priebe <s.priebe@profihost.ag>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: clm@fb.com
Subject: Re: kernel 4.1: no space left on device
Date: Sat, 18 Jul 2015 20:18:56 +0200 [thread overview]
Message-ID: <55AA9890.1040606@profihost.ag> (raw)
In-Reply-To: <558EC1F4.1050301@profihost.ag>
Still nobody? Upgraded to 4.2-rc2 and i still see the out of space
situation on two 30TB und 40TB arrays every week.
Stefan
Am 27.06.2015 um 17:32 schrieb Stefan Priebe:
> 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?
>
> Greets,
> Stefan
prev parent reply other threads:[~2015-07-18 18:18 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
[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 [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=55AA9890.1040606@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=clm@fb.com \
--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 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).