Hans van Kranenburg posted on Sun, 28 May 2017 02:59:57 +0200 as excerpted:
>> Note that our metadata is still DUP, and it doesn't have skinny extent >> tree metadata yet. It was originally created with btrfs-progs 3.17, and >> when we realized we should have single it was too late. I want to >> change that and see if I can convert on a NetApp clone. This should >> reduce extent tree metadata size by maybe more than 60% and >> whoknowswhat will happen to the abhorrent write traffic. > > Yeah, blabla... Converting metadata from DUP to single is a big no go > with btrfs balance, that's what I clearly got figured out now. Umm... Did you try -f (force)? See the manpage. OTOH, I'd have thought that was obvious enough you'd have tried it which would make the problem here something not so simple, but then again, I'd have thought you'd mention trying it too, if you did, to prevent exactly this sort of followup. So I don't know what to think, except I think it's worth covering the possibility just in case. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
