Noah Massey posted on Wed, 08 Jul 2015 16:02:04 -0400 as excerpted: > Standard disclaimer: Not a developer, just a user.
Same here. =:^) > The 1.5 GB ISO on a fresh ext4 system made me think of > http://thread.gmane.org/gmane.comp.file-systems.btrfs/36955 (ext4 > extents over 1 GB causing ENOSPC). > > Did the "btrfs filesystem balance" specify a "-t 900G" or similar? > > Or has that issue been fixed? Don't know about bug fixed, but that balance command syntax is definitely very deprecated, and there's no -t option documented for btrfs balance start, the current version. Did you mean btrfs filesystem defrag? It has a -t option that looks like it might have been what you were after. However, until very recently (I think it's in integration but don't know if it's in an actual release yet), there was an integer overflow bug with the -t option, such that if given a value above 3G, (I believe the cutoff is actually 4G, so something like 3999M would work), it would behave as if -t0 had been given. =:^( But the effective high value is typically 1G anyway, so the workaround is simple enough, just use -t 1G or -t 2G. That's what the patch effectively does anyway, reduce anything higher to 1G or 2G, IDR which. So if you meant btrfs filesystem defrag -t, a 2G value would be preferable to a 900G value, with the latter very likely not working as intended. -- 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
