From: Nix <nix@esperi.org.uk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Igor Pavlenko <ipavlenko.mail@gmail.com>, linux-bcache@vger.kernel.org
Subject: Re: bcache crashes at boot time
Date: Wed, 21 Jun 2017 12:05:26 +0100 [thread overview]
Message-ID: <87k245vbwp.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1706202158180.17052@mail.ewheeler.net> (Eric Wheeler's message of "Tue, 20 Jun 2017 22:04:40 +0000 (UTC)")
On 20 Jun 2017, Eric Wheeler uttered the following:
> On Mon, 5 Jun 2017, Igor Pavlenko wrote:
>
>> [ 45.941155] bcache: register_bdev() registered backing device sda3
>> [ 46.138238] bcache: error on 471776aa-1b34-4eff-ba7d-509a9554b43d:
>> inconsistent ptrs: mark = 3, level = 0, disabling caching
>
> ^^^
>
> This is the reason, something was inconsistent enough that it couldn't
> continue.
I'm rather worried about this sort of thing, given that I got it after
my first cache population and less than a week using bcache in anger.
The system in question is an oldie that restarts by mounting as much as
it can readonly and then doing a reboot (when bcache would routinely
whine about timeouts): the things it manages to remount readonly does
not usually include / is bcache usually unhappy about this sort of
thing? Would it prefer it if I was able to unmount it properly? If so,
it's time to upgrade that machine... it's only that I've had an oops
before now when stopping bcaches (early in test, not preserved because I
thought I'd made a mistake), so I thought it might be unhappy about
*that*, as well.
--
NULL && (void)
next prev parent reply other threads:[~2017-06-21 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 12:38 bcache crashes at boot time Igor Pavlenko
2017-06-20 22:04 ` Eric Wheeler
2017-06-21 11:05 ` Nix [this message]
2017-06-21 17:10 ` Kai Krakow
2017-06-21 21:57 ` Nix
2017-06-22 0:47 ` Eric Wheeler
2017-06-22 11:24 ` Nix
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=87k245vbwp.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=bcache@lists.ewheeler.net \
--cc=ipavlenko.mail@gmail.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.