Hi, On Fri, Sep 14, 2018 at 10:46:12PM +0500, Roman Mamedov wrote: > On Fri, 14 Sep 2018 19:27:04 +0200 > Rafael Jesús Alcántara Pérez <ralcant...@idedalo.com> wrote: > > > BTRFS info (device sdc1): use lzo compression, level 0 > > BTRFS warning (device sdc1): 'recovery' is deprecated, use > > 'usebackuproot' instead > > BTRFS info (device sdc1): trying to use backup root at mount time > > BTRFS info (device sdc1): disk space caching is enabled > > BTRFS info (device sdc1): has skinny extents > > BTRFS error (device sdc1): super_total_bytes 6010266660864 mismatch with > > fs_devices total_rw_bytes 6010266663424 > > There is a recent feature added to "btrfs rescue" to fix this kind of > condition: https://patchwork.kernel.org/patch/10011399/ > > You need a recent version of the Btrfs tools for it, not sure which, I see > that it's not in version 4.13 but is present in 4.17.
btrfs-progs_4.17-1~bpo9+1_amd64.changes is waiting to pass through NEW (due to the new library packages in the backport). It will take between 24h and several weeks to pass to stretch-backports. The variability in expected delivery is because a Debian FTP Master will need to manually ACK the changes. If 4.17.1 is required, please 'reportbug btrfs-progs' and take care to set the "found" version to 4.17-1, plus provide a citation for why 4.17.1 is required--without this justification the bug severity could be downgraded to wishlist. This hypothetical bug would be for the "unstable" suite (packages migrate to testing after a period of testing, and then become eligible for backporting). Take care! Nicholas
signature.asc
Description: PGP signature
