On 11/02/2014 01:48 AM, Roman Mamedov wrote:
But afaik balance with -mconvert=raid1 (and no other filters specified)
shouldn't touch data at all, no?
Ah... you seem to be correct. 8-)
My reading was flawed. I thought that the absence of a -d filter implied
an "unfiltered activity" (e.g. do it all) not no activity at all. That
is I was reading those as "filter expressions" not "enable expressions
with optional filters".
The manual is less than clear.
The usage output is more clear.
By the usage reading (and after checking the code):
Specifying no flags is asking to do everything. So "btrfs balance /path"
looks at every chunk.
Specifying none of -d -m and -s is the same as specifying all of them,
so "btrfs balance /path" and "btrfs balance -d -m -s /path" are the same
operation.
Specifying any of -d -m and/or -s highlights the absence of those not
specified.
Confusing bit, for example, from wiki
[QUOTE]
If you are getting out of space errors due to metadata being full, try
btrfs balance start -v -dusage=0 /mnt/btrfs
[/QUOTE]
Combined with "Balances only block groups with usage under the given
percentage. "
Which I was reading -dusage=0 means don't bother with data chunks and
(and so just fix the metadata), otherwise the mention of using a -d
filter to affect metadata is perverse.
Blarg... I mean just... blarg...
But now I know. 8-)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
