From: Kent Overstreet <kent.overstreet@gmail.com>
To: Marcin <marcin@mejor.pl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] BUG: soft lockup - CPU#0 stuck for 22s! [bch_copygc_read:5328]
Date: Mon, 5 Sep 2016 18:24:07 -0800 [thread overview]
Message-ID: <20160906022407.vukmxltjiyq3hn5s@kmo-pixel> (raw)
In-Reply-To: <c3e7064966b0449f5107bf3cb637c308@mejor.pl>
On Sun, Sep 04, 2016 at 08:21:17PM +0200, Marcin wrote:
> W dniu 2016-09-04 02:17, Kent Overstreet napisał(a):
>
> Hi!
>
> > On Sat, Sep 03, 2016 at 11:29:49PM +0200, Marcin wrote:
> > > Hi!
> > > Kernel at commit c820493652e830dc050e1418301e1bdec5691a1e
> > >
> > > I createt to devices, fast has size
> > > # blockdev --getsz /dev/sde1
> > > 20971520
> > > and slower device:
> > > # blockdev --getsz /dev/sdd1
> > > 2930209551
> > >
> > > I was copying files from one disk to bcache, after some time I got:
> > > BUG: soft lockup - CPU#0 stuck for 22s! [bch_copygc_read:5328]
> >
> > Thanks for the report - can you run addr2line with your vmlinux file,
> > and the
> > RIP?
> >
> > addr2line -i -e vmlinux ffffffffc028795b
>
> It returned:
> ??:0
>
> Probably due to I'm using bcache as module.
> <long story>
> As I mentioned before I wasn't sure which branch I used to test.
In case I didn't mention before - bcache-dev. This bug in the bcache-encryption
branch is a bit disconcerting though since my tests never hit it, but don't
worry about it - I'll chase it down.
> Please look at line with "bucket size":
> bucket_size: 768
> If bucket size is higher than (probably) 512 then I can't mount simple
> (without tiering) bcachefs filesystem. If I use such big device in tiered
> bcachefs I'm expieriencing random problems with stability of box.
> I think that bug in mail's subject is only random symptom of problem when
> device is formated with bucket size >512.
> What is going inside kernel in this case, is overwittem memory of other
> processes?
Whoops - that one is a bug in bcache-tools, non power of two bucket sizes aren't
supported (might be someday, but aren't currently). I just pushed a fix for that
to bcache-tools.
next prev parent reply other threads:[~2016-09-06 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 21:29 [bcachefs] BUG: soft lockup - CPU#0 stuck for 22s! [bch_copygc_read:5328] Marcin
2016-09-03 21:57 ` Marcin
2016-09-04 0:17 ` Kent Overstreet
2016-09-04 18:21 ` Marcin
2016-09-06 2:24 ` Kent Overstreet [this message]
2016-09-06 11:08 ` Marcin Mirosław
2016-09-06 13:08 ` Kent Overstreet
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=20160906022407.vukmxltjiyq3hn5s@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=marcin@mejor.pl \
/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