From: Omar Sandoval <osandov@osandov.com>
To: Zirconium Hacker <jared.e.vb@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS error (device sda4): failed to read chunk tree: -5
Date: Thu, 17 Aug 2017 13:51:29 -0700 [thread overview]
Message-ID: <20170817205129.GD2459@vader> (raw)
In-Reply-To: <CALsQ4_wnfHtJ+Drn3DJsQxdkX9=ZYDqH_H=hi3BxdSrnDZpqmw@mail.gmail.com>
On Wed, Aug 16, 2017 at 06:25:54PM -0400, Zirconium Hacker wrote:
> Hi,
> This is my first time using a mailing list, and I hope I'm doing this right.
>
> $ uname -a
> Linux thinkpad 4.12.6-1-ARCH #1 SMP PREEMPT Sat Aug 12 09:16:22 CEST
> 2017 x86_64 GNU/Linux
> $ btrfs --version
> btrfs-progs v4.12
> $ sudo mount -o ro,recovery /dev/sda4 /mnt
> mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda4,
> missing codepage or helper program, or other error.
> $ dmesg | tail
> <snip>
> [ 1289.087439] BTRFS warning (device sda4): 'recovery' is deprecated,
> use 'usebackuproot' instead
> [ 1289.087440] BTRFS info (device sda4): trying to use backup root at mount time
> [ 1289.087442] BTRFS info (device sda4): disk space caching is enabled
> [ 1289.097757] BTRFS error (device sda4): failed to read chunk tree: -5
> [ 1289.135222] BTRFS error (device sda4): open_ctree failed
Errno 5 is EIO, are there any I/O errors in your logs?
prev parent reply other threads:[~2017-08-17 20:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 22:25 BTRFS error (device sda4): failed to read chunk tree: -5 Zirconium Hacker
2017-08-16 22:52 ` Chris Murphy
[not found] ` <CALsQ4_x13pBuZ0wDmO=28m6xAEXFjOkORJsxDeFASOeA5oDeLg@mail.gmail.com>
[not found] ` <CAJCQCtRTiZy2YNZNLLx_KWuLMuNxPK26u1Orz91MqtDRFNRVNg@mail.gmail.com>
[not found] ` <CALsQ4_xkiyWuwJ4mVOV7QhWx6RFD80Y23fDNdPam2UFpRi1Gxw@mail.gmail.com>
[not found] ` <CAJCQCtTx_i_PrqgRbA-P9+zKX926KKeT1nwAJT=dkr-qcOpCCg@mail.gmail.com>
[not found] ` <CALsQ4_wZLvdqHdKa9DyjRXTmf1CV47+11-O_SqLRQJoQDT+gqQ@mail.gmail.com>
[not found] ` <CAJCQCtRYxb4QdN__WcUX_Jhs=GyguwJV79pKUp4PYhC9h_H-xA@mail.gmail.com>
[not found] ` <CALsQ4_xWte-vOJD-ppOPkvfHpLtu_-24KZPj2H9Tp99S7jDGcw@mail.gmail.com>
[not found] ` <CAJCQCtR-+o_GA7fCfSe8Lfwp8h6FzfiSR=qz8ekc4=dy98mtiQ@mail.gmail.com>
[not found] ` <CALsQ4_zTdxgfN25pkbhtXfj5EMVUbZ2=FrUHUocNxjynHhYhuA@mail.gmail.com>
2017-08-17 16:53 ` Chris Murphy
2017-08-17 22:42 ` Qu Wenruo
2017-08-18 3:13 ` Zirconium Hacker
2017-08-18 3:49 ` Qu Wenruo
2017-08-22 2:28 ` Qu Wenruo
2017-08-18 4:10 ` Chris Murphy
2017-08-18 7:17 ` Zirconium Hacker
2017-08-18 8:15 ` Qu Wenruo
2017-08-18 8:47 ` Zirconium Hacker
2017-08-18 9:03 ` Qu Wenruo
2017-08-18 9:08 ` Zirconium Hacker
2017-08-18 9:19 ` Qu Wenruo
2017-08-18 9:29 ` Zirconium Hacker
2017-08-18 9:46 ` Qu Wenruo
2017-08-18 10:20 ` Zirconium Hacker
2017-08-18 11:32 ` Qu Wenruo
2017-08-18 15:00 ` Chris Murphy
2017-08-18 21:52 ` Zirconium Hacker
2017-08-18 23:21 ` Qu Wenruo
2017-08-19 2:28 ` Zirconium Hacker
2017-08-19 3:45 ` Zirconium Hacker
2017-08-17 20:51 ` Omar Sandoval [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=20170817205129.GD2459@vader \
--to=osandov@osandov.com \
--cc=jared.e.vb@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).