From: Josef Bacik <jbacik@fb.com>
To: Goswin von Brederlow <goswin-v-b@web.de>, <linux-btrfs@vger.kernel.org>
Subject: Re: ENOSPC with 270GiB free
Date: Tue, 18 Feb 2014 08:58:10 -0500 [thread overview]
Message-ID: <530366F2.2010009@fb.com> (raw)
In-Reply-To: <20140216135808.GA1491@frosties>
-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTA2bsAAoJEANb+wAKly3BLB4P/0W5RCk9YZQ+WJcDs8/g82Be
G5oWx+0N2eYKIttCWxrvXlx2mpVP5mWimzYqs+V7SvaVgbm3KlwuID9JQpuOQ1lH
ihnxr48kdwNa8J159oEU7oVRJ84D1b0D21MZzIKU9YoNoDHTQQsELe4aojniKMIY
4RFh/8qWjMm2BGKW4jZwKzIHoF9rt+kU7Lhfm9XOi0OCut8FlFSjSwsiaN8NFJAf
DFtkgfZTRJUxiq3dXn7m6yzspS3L5atAfd862UbFDrA7EcYIZnc+zw9/hUxX8JwP
N3espmJQ03DRn8LLoOZtBMZ+NUnRgoOd33k1z9jeB7RnqN165vSQaYibUw6Zk+Vh
qADBAy+f8aHtBF8yNIuwqEXH9D5fXlfgYUnWW/YBiw6+dbguxb4CKIzkdh67paah
zvpLrXkZd95taqXFkaj0PZydwSVkSIbrPuNllRku02Bz8XxPjE0rlW+wCr2uHI2y
Ne2jpGdCClJCfLTZC8SsHaLeYktvEVBnQ6ZOriU+Rl1hzvi+ieG7leRHIa1K7VED
669zuZ4QfYvdU7lnXzTuC36NmmaSC4wrLaYTPAytU4OLB5dIby9nyF+25t60hq5n
pb2R5tn7heH9928aVktFMTuAWUBTI7B1O1ZGB/cTcYKduYXOD9Y5ljEalA7HhUpb
PwuiepAP1uBkiBPQDYH1
=tCLT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-18 13:58 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 [this message]
2014-02-18 18:16 ` Goswin von Brederlow
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=530366F2.2010009@fb.com \
--to=jbacik@fb.com \
--cc=goswin-v-b@web.de \
--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).