> On Mon, Jan 19, 2015 at 5:13 PM, Gareth Pye <gar...@cerberos.id.au> wrote: > I just tried from a slightly different tack, after doing another > -dusage=2 pass I did the following: > # btrfs balance start -v -dconvert=raid1 -dsoft -dusage=96 /data > Dumping filters: flags 0x1, state 0x0, force is off > DATA (flags 0x302): converting, target=16, soft is on, usage=96 > Done, had to relocate 0 out of 3763 chunks > # btrfs balance start -v -dconvert=raid1 -dsoft -dusage=99 /data > Dumping filters: flags 0x1, state 0x0, force is off > DATA (flags 0x302): converting, target=16, soft is on, usage=99 > ERROR: error during balancing '/data' - No space left on device
I guess I don't really understand the purpose of combining dconvert and dusage. Sure, it should either work or give an error, so there may still be a bug here. But I'm just not following why they'd be used together, seems superfluous. What happens when they're tried separately? I'm not sure which one's instigating the problem. Also I think you should upgrade to btrfs-progs 3.18, seeing as 3.12 is old and if there's a bug in that version of progs vs the kernel, it's not going to get fixed. -- Chris Murphy -- 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
