From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Kent Overstreet <kmo@daterainc.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>
Subject: Re: 3.18.3 + latest bcache-dev
Date: Wed, 21 Jan 2015 17:45:53 +0100 [thread overview]
Message-ID: <20150121164553.GA15237@cuci.nl> (raw)
In-Reply-To: <20150121110400.GA14729@cuci.nl>
Well, what I did was:
- Take out sdg.
- Reformat both caching and backing devices and started over.
I still have the kernel logs of the previous fault condition, but
not the data anymore.
What I notice are:
- The 100% CPU usage for four bcache_writebac processes is back. I've
already tried raising the value you suggested from 30 to 60, but I did
not have an opportunity to reboot yet. Will report back on this.
- When I run bcache-super-show on the backing devices, it works just fine.
- When I run bcache-super-show on the caching devices (while in service)
I get something like this:
sb.magic ok
sb.first_sector 8 [match]
sb.csum FFFFFFFF5D55BF8D [expected 726D3B42D08769EC]
Corrupt superblock (bad csum)
On both caching devices. Is this to be expected?
--
Stephen.
next prev parent reply other threads:[~2015-01-21 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 1:24 3.18.3 + latest bcache-dev Stephen R. van den Berg
2015-01-21 8:00 ` Kent Overstreet
2015-01-21 11:04 ` Stephen R. van den Berg
2015-01-21 16:45 ` Stephen R. van den Berg [this message]
2015-01-22 12:33 ` patch (Re: 3.18.3 + latest bcache-dev) Stephen R. van den Berg
2015-01-22 12:56 ` Stephen R. van den Berg
2015-01-21 22:47 ` 3.18.3 + latest bcache-dev Slava Pestov
2015-01-21 23:04 ` Stephen R. van den Berg
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=20150121164553.GA15237@cuci.nl \
--to=srb@cuci.nl \
--cc=kmo@daterainc.com \
--cc=linux-bcache@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 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.