From: Pavel Goran <via-bcache@pvgoran.name>
To: linux-bcache@vger.kernel.org
Subject: Re: INFO: task bcache_writebac:1582 blocked for more than 120 seconds
Date: Thu, 12 Jun 2014 02:35:11 +0700 [thread overview]
Message-ID: <19010378287.20140612023511@pvgoran.name> (raw)
In-Reply-To: <CADUHXCchuOVOY7vKzo8OnFmJhQWz6=RyJvhrwJm3y_N300mC8w@mail.gmail.com>
Hello Nik,
Wednesday, June 11, 2014, 9:48:20 PM, you wrote:
> I have been running bcache in writeback mode for a while, and had an
> unclean shutdown due to a power outage. Machine rebooted, did an
> fsck, everything seemed ok, I had a few corrupt files that were open
> when the shutdown happened, but no major deal. Then, I started
> getting hung tasks:
> INFO: task bcache_writebac:1582 blocked for more than 120 seconds.
This looks like a well-known bug that manifests itself with the
"bcache_writeback locked" messages. It's possible that your cache was
corrupted and disabled because of this, and now the bcache_writeback task has
no work to do and because of this the "locked" messages appear. (Personally I
get these messages when using a bcache device without cache.)
Bottom line: these messages probably appear because bcache is *already*
disabled.
> How can I disable bcache for now? The instructions to install it a
> pretty clear, but disabling it isn't.
Check whether cache is currently active:
cat /sys/block/bcache0/bcache/state
If it says "no cache", then there is no active cache on the bcache0 device. If
it says "clean", then the cache is there.
To disable bcache for the device bcache0 you need to issue the following
command:
echo "4faa930e-1983-45d3-ac40-e7dd0941d63c" | tee /sys/block/bcache0/bcache/detach
Substitute "4faa930e-1983-45d3-ac40-e7dd0941d63c" with the ID of your cache
(you can find cache IDs by looking at the /sys/fs/bcache directory).
Pavel Goran
prev parent reply other threads:[~2014-06-11 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 14:48 INFO: task bcache_writebac:1582 blocked for more than 120 seconds Nik Martin
2014-06-11 19:35 ` Pavel Goran [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=19010378287.20140612023511@pvgoran.name \
--to=via-bcache@pvgoran.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox