On Mon, Sep 04, 2017 at 08:42:29PM +0200, Adam Borowski wrote: > On Mon, Sep 04, 2017 at 07:07:25PM +0300, Timofey Titovets wrote: > > 2017-09-04 18:11 GMT+03:00 Adam Borowski <kilob...@angband.pl>: > > > Here's an utility to measure used compression type + ratio on a set of > > > files > > > or directories: https://github.com/kilobyte/compsize > > > > > > It should be of great help for users, and also if you: > > > * muck with compression levels > > > * add new compression types > > > * add heurestics that could err on withholding compression too much > > > > Packaged to AUR: > > https://aur.archlinux.org/packages/compsize-git/ > > Cool! I'd wait until people say the code is sane (I don't really know these > ioctls) but if you want to make poor AUR folks our beta testers, that's ok. > > However, one issue: I did not set a license; your packaging says GPL3. > It would be better to have something compatible with btrfs-progs which are > GPL2-only. What about GPL2-or-higher? > > After adding some related info (like wasted space in pinned extents, reuse > of extents), it'd be nice to have this tool inside btrfs-progs, either as a > part of "fi du" or another command.
I've now implemented a prototype that calculates the compressed size of extents per-file. As 'fi du' knows about what extents are shared, the compression can be also calculated shared/exclusive. There's no summary like compsize does, this would need a bit more precise tracking of the extents, not just the compressed size but also which algo was used. I can imagine all sorts of output enhancements, like summarize the inline-compressed extents or print the algo summary per-file. This should be easy once the calclation code is there. I haven't reused compsize.c, as I needed only the ioctl part and wire it to 'fi du', but the search ioctl is the same. -- 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
