From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: raid10 array lost with single disk failure?
Date: Sat, 8 Jul 2017 19:37:42 +0000 (UTC) [thread overview]
Message-ID: <pan$6b094$f0581f40$6591029b$d3b08010@cox.net> (raw)
In-Reply-To: CACzgC9i4Eb2=xKpF02Czr432r1WQkhTx+8tZswsgw5EUfofJsg@mail.gmail.com
Adam Bahe posted on Fri, 07 Jul 2017 23:40:20 -0500 as excerpted:
> Some additional information. I am running Rockstor just like Daniel
> Brady noted in his post just before mine titled "Chunk root problem".
> Sorry I am somewhat unfamiliar with newsgroups so I am not sure how to
> reply to his thread before I was subscribed. But I am noticing something
> in my logs very similar to his, I get:
>
> [ 716.902506] BTRFS error (device sdb): failed to read the system
> array: -5
> [ 716.918284] BTRFS error (device sdb): open_ctree failed
> [ 717.004162] BTRFS warning (device sdb): 'recovery' is deprecated,
> use 'usebackuproot' instead
> [ 717.004165] BTRFS info (device sdb): trying to use backup root at
> mount time
> [ 717.004167] BTRFS info (device sdb): disk space caching is enabled
> [ 717.004168] BTRFS info (device sdb): has skinny extents
> [ 717.005673] BTRFS error (device sdb): failed to read the system
> array: -5
> [ 717.020248] BTRFS error (device sdb): open_ctree failed
>
> He also received a similar open_ctree failed message after he upgraded
> his kernel on Rockstor to 4.10.6-1.el7.elrepo.x86_64 and
> btrfs-progs-4.10.1-0.rockstor.x86_64.
FWIW that's not significant. Open ctree failed is simply the generic
btrfs failure to mount message. It tells you nothing of the real
problem, so other clues must be used to discern that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-07-08 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 4:26 raid10 array lost with single disk failure? Adam Bahe
2017-07-08 4:40 ` Adam Bahe
2017-07-08 19:37 ` Duncan [this message]
2017-07-08 20:51 ` Duncan
2017-07-09 23:13 ` Ferry Toth
2017-07-10 2:13 ` Adam Bahe
2017-07-10 12:49 ` Austin S. Hemmelgarn
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='pan$6b094$f0581f40$6591029b$d3b08010@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).