From: Nicholas Steeves <nsteeves@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Stefan Malte Schumacher <stefan.m.schumacher@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Size of scrubbed Data
Date: Fri, 16 Sep 2016 08:21:48 -0400 [thread overview]
Message-ID: <20160916122148.GA17713@DigitalMercury.dynalias.net> (raw)
In-Reply-To: <CAJCQCtR6bcBjK+Npd1+8KOYFOp5GWUBQ8hxvjwNU7vEaLHH9Hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Thank you for the assistance Chris :-)
On 15 September 2016 at 17:18, Chris Murphy <lists@colorremedies.com> wrote:
>> On Thu, Sep 15, 2016 at 9:48 AM, Stefan Malte Schumacher
>> <stefan.m.schumacher@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
).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-16 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 15:48 Size of scrubbed Data Stefan Malte Schumacher
2016-09-15 20:11 ` g6094199
2016-09-15 21:10 ` Stefan Malte Schumacher
2016-09-15 21:18 ` Chris Murphy
2016-09-16 12:21 ` Nicholas Steeves [this message]
2016-09-17 11:02 ` Stefan Malte Schumacher
2016-09-17 13:27 ` Adam Borowski
2016-09-17 14:34 ` Tim Walberg
2016-09-17 15:08 ` Tim Walberg
2016-09-17 15:24 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160916122148.GA17713@DigitalMercury.dynalias.net \
--to=nsteeves@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=stefan.m.schumacher@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.