E V posted on Thu, 16 Feb 2017 15:13:40 -0500 as excerpted: > I can delete a multi GB file and get several GB of unallocated space, > however if I try and copy big files to it again the same exact thing > happens. However, if I play with balance and deleting files and such and > manage to get it to allocate another metadata chunk while there is > unallocated space then the filesystem will happily fill up all of the > data chunks. Failing an automatic allocation out of global reserve, or > saving metadata as soon as unallocated space is available it would be > nice if I could just delete a file and then tell btrfs to allocate more > metadata immediately. Makes sense? No idea how easy this would be to do, > but seems like it should be a simple thing btrfs file could do.
You should be able to trigger metadata allocation by writing enough tiny files, say 1 KiB each. Small files (typically upto slightly under 2 KiB) are inlined into the metadata, thus using it up. Writing enough of them in for instance a shellscript loop to trigger a new metadata chunk allocation shouldn't be too difficult, but keep in mind when doing the math that global reserve is allocated from metadata as well, tho it's single even when metadata is dup or (as here) raid1. Also, if you're looking at the space output as you write them, keep in mind the btrfs 30-second by default commit timing, and call btrfs fi sync (or just sync but that's system-wide) on the filesystem every N files or so, before checking the usage, so it's accurate without waiting 30 seconds for the commit-clock to timeout. -- 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
