On Thu, Jun 09, 2016 at 06:52:23PM +0200, Christoph Anton Mitterer wrote: > On Thu, 2016-06-09 at 19:46 +0300, Roman Lebedev wrote: > > No-no-no. > > I did not mean installing the cron job by default. > > I meant providing such job in /usr/share/doc/btrfs-progs/ as a > > example > That's fine of course. > > I'd even say its okay if this was actually installed in > /etc/cron<something> debconf(igurable), defaulting to not being enabled > with some low priority. > > > Even better would of course be, if such cronjob would be merged > upstream where it's properly maintained across distros... but since > Marc is very well known on the list and so his scripts, I guess > upstream hasn't too much interest in including > maintenance/administration tools that go beyond the bare stuff.
I think btrfsmaintenance is the defacto cross-distro solution. The Debian package recently (finally!) made it through NEW and into experimental. It is well tested on OpenSUSE and SLED, and systemd timer support seems like it will soon be merged from this pull request: https://github.com/kdave/btrfsmaintenance/pull/36 Links: https://packages.debian.org/experimental/btrfsmaintenance * currently not displaying due to a 500 error https://anonscm.debian.org/collab-maint/btrfsmaintenance.git The upstream model is a bit strange because it uses btrfsmaintenance-refresh.service (using btrfsmaintenance-refresh-cron.sh) to update links in /etc/cron.{daily,weekly,monthly}; however, on the upside this made it easy to configure maintenance operations to be disabled by default. Maintenance operations are disabled by default on the master branch, but I've enabled them on the experimental branch. If no one objects, I'd like to reassign this bug to the btrfsmaintenance package. Cheers, Nicholas
signature.asc
Description: PGP signature
