From: Marc MERLIN <marc@merlins.org>
To: Eric Wheeler <lists@ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: every boot gives: bcache/alloc.c:78 WARNING
Date: Wed, 3 Aug 2016 17:33:51 -0700 [thread overview]
Message-ID: <20160804003351.GI31234@merlins.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1608031707300.10662@mail.ewheeler.net>
On Wed, Aug 03, 2016 at 05:26:30PM -0700, Eric Wheeler wrote:
> On Wed, 3 Aug 2016, Marc MERLIN wrote:
>
> > This happens on all kernels up to 4.7.
> > Sorry, it happens earlier than ethernet coming up or my storage, so I can't
> > use netconsole or other text dumps:
> > https://goo.gl/photos/ubsi6maZXsjkevYY7
> >
> > Looks like the warning happens on the registration of one of my bcache, but
> > I can't tell which one or why.
> >
> > Does the trace give any hints?
> > (please ignore the load modules errors below, different issue)
>
> Does it cause a problem, or just warn?
No problem, but since it's a warning, I'm reporting it.
> It looks like something needs garbage collected but perhaps isn't.
>
> You could write to sysfs/.../trigger_gc:
>
> https://evilpiepirate.org/git/linux-bcache.git/tree/Documentation/bcache.txt
> trigger_gc
> Writing to this file forces garbage collection to run.
BTW both this and the just released 4.7.0 are still missing the
documentation updates I contributed months ago. Any idea what's going on
there?
> If that doesn't work, I wonder what increasing BUCKET_GC_GEN_MAX would do,
> though I don't know if that is safe. Its set to 96U, so its not on on a
> bit boundary which sounds like it could be slightly safer---but I wouldn't
> try it unless this is a test machine.
That's on the backing device, correct?
I have 3 of them, and I can only write to them way way later in the boot
process.
Should I do that one by one and see if I get output now?
Thanks,
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/
next prev parent reply other threads:[~2016-08-04 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:19 every boot gives: bcache/alloc.c:78 WARNING Marc MERLIN
2016-08-04 0:26 ` Eric Wheeler
2016-08-04 0:33 ` Marc MERLIN [this message]
2016-08-04 1:43 ` Eric Wheeler
2016-08-04 2:44 ` Eric Wheeler
2016-08-04 3:23 ` Marc MERLIN
2016-08-04 4:32 ` Eric Wheeler
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=20160804003351.GI31234@merlins.org \
--to=marc@merlins.org \
--cc=linux-bcache@vger.kernel.org \
--cc=lists@ewheeler.net \
/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).