From: Marcin <marcin@mejor.pl>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] problem with `bcache fsck`
Date: Fri, 17 Mar 2017 09:57:32 +0100 [thread overview]
Message-ID: <4662ab7db9e440f044e98c0aea6b63c0@mejor.pl> (raw)
In-Reply-To: <20170316235651.oehere2zxhewbbdh@moria.home.lan>
W dniu 2017-03-17 00:57, Kent Overstreet napisał(a):
> On Thu, Mar 16, 2017 at 11:07:20PM +0100, Marcin wrote:
>> If I add bcachefs to fstab openrc expects userland fsck to works this
>> is why
>> I tried it to use.
>
> Fsck should be fixed now
Thanks, but when I pass only one device from two used in tiered fs
`bcache fsck` becomes upset:
# bcache fsck /dev/sdd1
bcache: libbcache/buckets.h:87: gen_after: Assertion `!(r > 128U)'
failed.
Also it happened I got segfault while using fsck. I don't have coredump,
I'll try to catch it.
Marcin
next prev parent reply other threads:[~2017-03-17 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:16 [bcachefs] problem with `bcache fsck` Marcin
2017-03-16 20:34 ` Kent Overstreet
2017-03-16 22:07 ` Marcin
2017-03-16 23:57 ` Kent Overstreet
2017-03-17 8:57 ` Marcin [this message]
2017-03-17 22:06 ` Marcin
2017-03-17 22:26 ` Marcin
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=4662ab7db9e440f044e98c0aea6b63c0@mejor.pl \
--to=marcin@mejor.pl \
--cc=kent.overstreet@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox