Thanks for the information. I did another run of scrubbing et voila:
total bytes scrubbed: 12.11TiB with 0 errors, which is pretty much two
times the amount of actual data stored on the filesystem. I am
relieved, but still would like to know why this went wrong in the
first place and why it is working again without me doing anything to
fix it.
Concerning Testing: I only use it on desktops and home servers, which
do not offer any services to the net. I am very fond of Debian and
always use stable or even old-stable on work servers, but was finally
to annoyed at the fact that the software I was using on a fresh
installation was practically already out of date.

Yours sincerely

2016-09-16 14:21 GMT+02:00 Nicholas Steeves <nstee...@gmail.com>:
> Thank you for the assistance Chris :-)
> On 15 September 2016 at 17:18, Chris Murphy <li...@colorremedies.com> wrote:
>>> On Thu, Sep 15, 2016 at 9:48 AM, Stefan Malte Schumacher
>>> <stefan.m.schumac...@gmail.com> wrote:
> ...
>>> I believe it may be a result of replacing my old installation of
>>> Debian Jessie with Debian Stretch
> ...
>>> btrfs --version
>>> btrfs-progs v4.7.1
>> Upgrade to 4.7.2 or downgrade to 4.6.1 before using btrfs check; see
>> the changelog for details. I'm not recommending that you use btrfs
>> check, just saying this version of tools is not reliable for some
>> file systems.
> Hi Stefan, as far as I can tell 4.7.2 is currently blocked from
> migrating from unstable to testing due to a glibc version transition,
> so the easiest thing to do is to get fall back on 4.6.1 found here:
> http://snapshot.debian.org/package/btrfs-progs/4.6.1-1/
> Cheers,
> Nicholas
> P.S. You're brave to run testing before the soft-freeze!  Occasionally
> security fixes in sid can't propagate to testing, because a transition
> like this is in progress ( https://www.debian.org/security/faq#testing
> ).
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

Reply via email to