From: Nils Steinger <nst@voidptr.de>
To: Patrik Lundquist <patrik.lundquist@gmail.com>,
Christian Pernegger <pernegger@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: "WARNING: device 0 not present" during scrub?
Date: Wed, 2 Mar 2016 22:50:49 +0100 [thread overview]
Message-ID: <56D76039.2020009@voidptr.de> (raw)
In-Reply-To: <CAA7pwKNH=HkfCLYtxaFSte7eg2vdwumyzddD9WPwn28i9xmuqA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]
On 01.02.2016 11:23, Patrik Lundquist wrote:
> apt-get install -t jessie-backports linux-image-4.3.0-0.bpo.1-amd64
>
> Or something like that for the image name. Unfortunately there's no
> stable backport of btrfs-tools (as they call btrfs-progs).
There is now: 4.4-1~bpo8+1
Upgrading from btrfs-tools 3.17 to 4.4 fixed the scrub aborts for me.
Oddly, `btrfs scrub start -B /dev/mapper/foo` terminates with exit code
0 when it aborts due to the "device 0" problem.
That's not supposed to happen, is it?
> EXIT STATUS
> btrfs scrub returns a zero exit status if it succeeds. Non zero
> is returned in case of failure.
Regards,
Nils Steinger
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-03-02 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 11:59 "WARNING: device 0 not present" during scrub? Christian Pernegger
2016-01-30 20:10 ` Henk Slager
2016-01-30 21:19 ` Christian Pernegger
2016-01-31 1:42 ` Chris Murphy
2016-01-31 12:35 ` Christian Pernegger
2016-01-31 18:06 ` Henk Slager
2016-02-01 1:59 ` Duncan
2016-02-01 3:23 ` Chris Murphy
2016-01-31 1:09 ` Chris Murphy
2016-02-01 10:23 ` Patrik Lundquist
2016-03-02 21:50 ` Nils Steinger [this message]
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=56D76039.2020009@voidptr.de \
--to=nst@voidptr.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=patrik.lundquist@gmail.com \
--cc=pernegger@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.