From: Marc MERLIN <marc@merlins.org>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Zhu Yanhai <zhu.yanhai@gmail.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Christoph Nelles <evilazrael@evilazrael.de>,
linux-bcache@vger.kernel.org
Subject: Re: BUG: drivers/md/bcache/writeback.c:237
Date: Fri, 26 Feb 2016 08:27:05 -0800 [thread overview]
Message-ID: <20160226162705.GA18927@merlins.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1602260422290.3635@mail.ewheeler.net>
On Fri, Feb 26, 2016 at 04:55:02AM +0000, Eric Wheeler wrote:
> According to Documentation/bcache.txt:
> "" If you're booting up and your cache device is gone and never
> coming back, you can force run the backing device:
> echo 1 > /sys/block/sdb/bcache/running
> [...]
> The backing device will still use that cache set if it shows up
> in the future, but all the cached data will be invalidated. ""
>
> So it seems that you are safe. (It would be interesting to know how it
> invalidates the cache. Maybe bumps the Set UUID? Not sure.)
Yeah, that was my understanding too, but I wanted to make sure.
Strangely (worringly so?) the cache was replayed at boot, and this time
nothing crashed, or any traceback.
Now I'm wondering if it pushed garbage onto my filesystem :-/
Again, no netconsole, sorry, this happens before my ethernet interface
comes up.
https://goo.gl/photos/suqp9sHyijdt9iUG7
sda6 was the partition I hid and just came back.
sdb1 is the bcache linked to it.
On the plus side, no crash, although this didn't get to exercise your
new code either.
Either way, I'm really starting to have mixed feelings about using
writeback if it's going to give me random crashes and subsequent
corruption (which is a risk listed in the doc, admittedly).
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2016-02-26 16:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 6:04 echo dev > /sys/fs/bcache/register gives page allocation failure: order:4, mode:0x2040d0 Marc MERLIN
2016-02-15 12:02 ` Johannes Thumshirn
2016-02-15 15:32 ` Marc MERLIN
2016-02-15 15:45 ` Christoph Nelles
2016-02-23 16:32 ` Marc MERLIN
2016-02-23 20:57 ` Marc MERLIN
2016-02-24 20:45 ` BUG: drivers/md/bcache/writeback.c:237 Marc MERLIN
2016-02-25 0:58 ` Eric Wheeler
2016-02-25 6:41 ` Eric Wheeler
2016-02-25 7:36 ` Eric Wheeler
2016-02-25 10:08 ` Zhu Yanhai
2016-02-26 2:38 ` Eric Wheeler
2016-02-26 2:46 ` Marc MERLIN
2016-02-26 3:19 ` Marc MERLIN
2016-02-26 4:55 ` Eric Wheeler
2016-02-26 16:27 ` Marc MERLIN [this message]
2016-02-26 21:17 ` Eric Wheeler
2016-03-03 4:17 ` Eric Wheeler
2016-03-03 4:25 ` Marc MERLIN
2016-02-25 10:18 ` Zhu Yanhai
2016-02-25 15:20 ` Marc MERLIN
2016-02-25 23:44 ` Eric Wheeler
2016-02-26 0:17 ` Marc MERLIN
2016-02-15 12:11 ` echo dev > /sys/fs/bcache/register gives page allocation failure: order:4, mode:0x2040d0 Kent Overstreet
2016-02-24 6:53 ` Eric Wheeler
2016-02-24 16:37 ` Disabling bcache from boot when it crashes? Marc MERLIN
2016-02-24 19:10 ` Eric Wheeler
2016-02-25 5:48 ` Marc MERLIN
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=20160226162705.GA18927@merlins.org \
--to=marc@merlins.org \
--cc=bcache@lists.ewheeler.net \
--cc=evilazrael@evilazrael.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=zhu.yanhai@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.