Upstream software project

btrfsmaintenance

Scripts for btrfs periodic maintenance tasks

About btrfsmaintenance

Scripts for btrfs periodic maintenance tasks

This project links 7 native package records across 7 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

btrfsmaintenance repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.btrfsmaintenance: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
btrfsmaintenance
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-only
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Scripts for btrfs maintenance tasks like periodic scrub, balance, trim or defrag on selected mountpoints or directories. This is a set of scripts supplementing the btrfs filesystem and aims to automate a few maintenance tasks. This means the scrub, balance, trim or defragmentation. Each of the tasks can be turned on/off and configured independently. The default config values were selected to fit the default installation profile with btrfs on the root filesystem. Overall tuning of the default values should give a good balance between effects of the tasks and low impact of other work on the system. If this does not fit your needs, please adjust the settings.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package btrfsmaintenance

    bookworm (Debian 12 (Bookworm)) (admin): automate btrfs maintenance tasks on mountpoints or directories

    0.5-4: all

Debian 13 (Trixie)

  1. Package btrfsmaintenance

    trixie (Debian 13 (Trixie)) (admin): automate btrfs maintenance tasks on mountpoints or directories

    0.5.2-1: all

Fedora 43

  1. Package btrfsmaintenance

    43 (Fedora 43) (Unspecified): Scripts for btrfs maintenance tasks

    0.5.2-4.fc43: noarch

    Source: btrfsmaintenance

Fedora 44

  1. Package btrfsmaintenance

    44 (Fedora 44) (Unspecified): Scripts for btrfs maintenance tasks

    0.5.2-6.fc44: noarch

    Source: btrfsmaintenance

openSUSE Leap 15.6

  1. Package btrfsmaintenance

    leap-15.6 (openSUSE Leap 15.6) (System/Base): Scripts for btrfs periodic maintenance tasks

    0.4.2-3.3.1: noarch

    Source: btrfsmaintenance

openSUSE Leap 16.0

  1. Package btrfsmaintenance

    leap-16.0 (openSUSE Leap 16.0) (System/Base): Scripts for btrfs periodic maintenance tasks

    0.5-160000.2.2: noarch

    Source: btrfsmaintenance

openSUSE Tumbleweed

  1. Package btrfsmaintenance

    tumbleweed (openSUSE Tumbleweed) (System/Base): Scripts for btrfs periodic maintenance tasks

    0.5.2-2.4: noarch

    Source: btrfsmaintenance

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.