I tried defrag -c and it does nothing to files that have come in with strict allocate = yes.
On 22/08/2013 19:29, "Kai Krakow" <[email protected]> wrote: >Josef Bacik <[email protected]> schrieb: > >> Not sure what strict allocate = yes does, but I assume it probably does >> fallocate() in which case yeah we aren't going to compress, we'll just >> write >> into the preallocated space. We don't support compressed writes into >> preallocated space ATM, and I'm not sure we ever will. Thanks, > >Good to know, this renders btrfs as efficient storage backend for Windows >file shares pretty useless. Does this also happen with compress-force? > >As a work-around one could write a cronjob that regularly defrags all >files >changed since the last run with -c option... > >Thanks, >Kai > >-- >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 -- 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
