From: Goswin von Brederlow <goswin-v-b@web.de>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC with 270GiB free
Date: Tue, 18 Feb 2014 19:16:48 +0100 [thread overview]
Message-ID: <20140218181648.GA26848@frosties> (raw)
In-Reply-To: <530366F2.2010009@fb.com>
On Tue, Feb 18, 2014 at 08:58:10AM -0500, Josef Bacik wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/16/2014 08:58 AM, Goswin von Brederlow wrote:
> > Hi,
> >
> > I'm getting a ENOSPC error from btrfs despite there still being
> > plenty of space left:
> >
> > % df -m /mnt/nas3 Filesystem 1M-blocks Used Available
> > Use% Mounted on /dev/mapper/nas3-a 19077220 18805132 270773
> > 99% /mnt/nas3
> >
> > % btrfs fi show Label: none uuid:
> > 4b18f84e-2499-41ca-81ff-fe1783c11491 Total devices 1 FS bytes used
> > 17.91TiB devid 1 size 18.19TiB used 17.94TiB path
> > /dev/mapper/nas3-a
> >
> > Btrfs v3.12
> >
> > % btrfs fi df Data, single: total=17.89TiB, used=17.88TiB System,
> > DUP: total=32.00MiB, used=1.92MiB Metadata, DUP: total=25.50GiB,
> > used=24.89GiB
> >
> > As you can see there are still 270GiB free and plenty of block
> > groups free on the device too.
> >
> > So why isn't btrfs allocating a new block group to store more
> > data?
> >
> >
>
> What kernel? Can you give btrfs-next a try? Mount with -o
> enospc_debug and when you get enospc send the dmesg. Thanks,
>
> Josef
Standard Debian linux kernel:
Linux nas3 3.12-1-amd64 #1 SMP Debian 3.12.9-1 (2014-02-01) x86_64 GNU/Linux
Compiling new kernel and rebooting will take some time. But it looks
like I can remount with enospc_debug. I will try if that outputs
anything usefull first. So far I got:
[258988.006643] btrfs: disk space caching is enabled
MfG
Goswin
prev parent reply other threads:[~2014-02-18 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 13:58 ENOSPC with 270GiB free Goswin von Brederlow
2014-02-16 18:18 ` Duncan
2014-02-16 19:58 ` Goswin von Brederlow
2014-02-17 7:42 ` Dan van der Ster
2014-02-17 9:26 ` Goswin von Brederlow
2014-02-18 13:58 ` Josef Bacik
2014-02-18 18:16 ` Goswin von Brederlow [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=20140218181648.GA26848@frosties \
--to=goswin-v-b@web.de \
--cc=jbacik@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).