All of lore.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: Wed, 5 Mar 2014 22:13:10 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140305T190503-404@post.gmane.org> (raw)
In-Reply-To: 73124688-5EDF-4DB5-AC9E-9F365397DD28@colorremedies.com

Chris Murphy <lists <at> colorremedies.com> writes:

> You could also try a full defragment by specifying -r on the mount point
> with a small -t value to effectively cause everything to be subject
> to defragmenting. If this still doesn't permit soft rebalance, then maybe
> filefrag can find files that have more than 1 extent and just copy 
> them (make duplicates, delete the original). Any copy will be
> allocated into chunks with the new profile.

I would think so too.  But it doesn't seem to be happening. 
Here is an example with one file:

root@ossy:/mymedia# filefrag output.wav
output.wav: 2 extents found
root@ossy:/mymedia# /usr/src/btrfs-progs/btrfs fi de -t 1 /mymedia/output.wav 
root@ossy:/mymedia# filefrag output.wav
output.wav: 2 extents found

btrfs does not defrag the file. And copying the file usually
doesn't defrag it either:

root@ossy:/mymedia# cp output.wav output.wav.bak
root@ossy:/mymedia# filefrag output.wav.bak
output.wav.bak: 2 extents found

I even tried copying a large file to another filesystem (/dev/shm),
 removing the original, and copying it back, and more often than not 
it still had more than 1 extent. 

If I copy each file out to another filesystem and then back, will btrfs 
not use any of the space on the "single" and just re-allocate space 
on the RAID1 like I want it to?



  reply	other threads:[~2014-03-05 22:13 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
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 [this message]
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.20140305T190503-404@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 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.