public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Russo <mike@papersolve.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC errors during raid1 rebalance
Date: Tue, 4 Mar 2014 15:55:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140304T164456-762@post.gmane.org> (raw)
In-Reply-To: 20140303183911.GL13899@carfax.org.uk

Hugo Mills <hugo <at> carfax.org.uk> writes:

>    This is just a guess, but you might have some large (>1GB) 
extents
> in there that span across multiple chunks. I'd suggest running a 
btrfs
> defrag on any particularly big files and see if that helps the 
situation.
> 

Doing this is definitely helping, but I have to run the defrag multiple 
times with different values for "-t". If I don't include -t the defrag 
runs really quickly but doesn't seem to do anything.  Now I've gotten 
it down to only 2 5GB segments that won't move.  I'm going to 
extract the very big log generated when I run 
"btrfs ba start -dconvert=raid1,soft /mymedia" 
with enospc_debug and send it as a file, hopefully it will help.  
The first couple lines are:

Mar  4 10:49:23 ossy kernel: [134922.806764] BTRFS info (device sdd1): 
relocating block group 894460493824 flags 1
Mar  4 10:49:32 ossy kernel: [134931.650504] BTRFS error (device sdd1): 
allocation failed flags 17, wanted 1368420352
Mar  4 10:49:32 ossy kernel: [134931.650507] BTRFS: space_info 1 has 
113996488704 free, is not full
Mar  4 10:49:32 ossy kernel: [134931.650509] BTRFS: space_info 
total=1320702443520, used=1201311391744, pinned=0, 
reserved=565596160, may_use=1368420352, readonly=4828966912





  reply	other threads:[~2014-03-04 15:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 17:23 ENOSPC errors during raid1 rebalance Mike Russo
2014-03-03 18:16 ` Duncan
2014-03-03 18:24   ` Michael Russo
2014-03-03 18:48     ` Chris Murphy
2014-03-03 19:24       ` Michael Russo
2014-03-03 20:41         ` Chris Murphy
2014-03-03 20:50           ` Michael Russo
2014-03-03 21:02             ` Chris Murphy
2014-03-03 18:39 ` Hugo Mills
2014-03-04 15:55   ` Michael Russo [this message]
2014-03-04 17:29     ` Chris Murphy
2014-03-04 18:54       ` Michael Russo
2014-03-04 19:30         ` Chris Murphy
2014-03-05  0:27   ` Mike Russo
2014-03-05  3:32     ` Chris Murphy
2014-03-05 22:13       ` Michael Russo
2014-03-06  7:41         ` Duncan
2014-03-07  1:13           ` Michael Russo
2014-03-07  8:02             ` Hugo Mills
2014-03-07 10:18               ` Duncan
2014-03-07 14:17               ` Mike Russo
2014-03-08  1:46                 ` Mike Russo
2014-03-05  4:08     ` Chris Murphy
2014-03-05 22:13       ` Michael Russo
2014-03-06 17:07         ` Chris Murphy
  -- strict thread matches above, loose matches on Subject: below --
2014-03-13 22:38 Eugene Crosser

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=loom.20140304T164456-762@post.gmane.org \
    --to=mike@papersolve.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