Duncan 1i5t5.duncan at cox.net writes:
That allows rollback if desired, but does tie up some some space with the
automatically created btrfs snapshot that contains the ext3/4 metadata
and untouched data.
Nope, I definitely deleted the snapshots, running btrfs sub list
gives me nothing
Chris Murphy lists at colorremedies.com writes:
It might be worth adding enospc_debug as a mount option
These messages only appear when I mount with enospc_debug. I
included them as examples but I can post the full output later if
needed. As for whether btrfs-convert should be recommended, I
Chris Murphy lists at colorremedies.com writes:
Chris Murphy lists at colorremedies.com writes:
Gotcha. I think Hugo has the best next step. Defragment.
I think this is going to work. I cancelled a partial defrag
and did another move attempt, and this time
5GB got moved! So I'm going to
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,
Chris Murphy lists at colorremedies.com writes:
Based on my reading of the man page, I think it's expected.
You either need -s -l or -t.
Ok, although the man page uses [ ] instead of and something
does happen if I don't add them. But if I use -t 1 wouldn't that
get everything?
Now I've
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
Chris Murphy lists at colorremedies.com writes:
Did you do a defrag and balance after ext4btrfs conversion,
but before data/metadata profile conversion?
No I didn't, as I thought it was only optional and didn't realize
it might later affect my ability to change profiles.
--
To
Duncan 1i5t5.duncan at cox.net writes:
But if you're not using compression, /that/ can't explain it...
Ha! Well while that was an interesting discussion of fragmentation,
I am only using the default mount options here and so no compression.
The only reason I'm really even looking at the
