All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC with 270GiB free
Date: Sun, 16 Feb 2014 18:18:38 +0000 (UTC)	[thread overview]
Message-ID: <pan$3dcd9$71bbddfa$a9318b9a$e36a9655@cox.net> (raw)
In-Reply-To: 20140216135808.GA1491@frosties

Goswin von Brederlow posted on Sun, 16 Feb 2014 14:58:08 +0100 as
excerpted:

> 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?

I saw this on a much (much) smaller filesystem a few weeks ago, when I 
redid my /boot.  In my case it was under a gig total, so mixed-mode, but 
copying files over in a particular order errored some of them out with 
ENOSPC.  But the way I was copying (using mc) left the ones that hadn't 
copied selected, and I tried a copy of them again, and/or used mc's 
directory-diff to find the missing files and copy them over again.  After 
about three times, they all copied.

So some combination of size and metadata wasn't triggering a new block 
allocation, but coming in a different order, it triggered fine.  Again, 
this was mixed-mode, so data/metadata blocks mixed, and it didn't matter 
which ran out first since they were combined.

I wonder if you're running into something similar.  Can you try doing the 
copy in a different order, or is it one big file?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-02-16 18:19 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 [this message]
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

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='pan$3dcd9$71bbddfa$a9318b9a$e36a9655@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 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.