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 23:26:11 +0100 [thread overview]
Message-ID: <c63b4675d9f93acebad942c51d9c56f0@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
>
>> There is no new commit, I'm at
>> commit 7274700edcf99ab67d4f72eca4f07d0220b9abae
>> Author: Kent Overstreet <kent.overstreet@gmail.com>
>> Date: Tue Mar 14 21:07:39 2017 -0800
>>
>> bcache: fix device hot add
>
> Ok, you're good then (at least re: the buffered reads bug)
>
>> I suspect that problem is due to using --metadata_replicas=2. If you
>> have a
>> some spare time please try fileystsem formated with this parameters:
>> # bcache format --compression_type=gzip --metadata_replicas=2
>> --data_checksum_type=crc64 --metadata_checksum_type=crc64 --tier=2
>> /dev/sde1
>> --tier=3 /dev/sdd1
>
> Alright, will do
I configured logging using netconsole, I formated fs using favorite
killer-combo[1], when I copied ~480000 rather small files the host
rebooted. I only cought this:
Mar 17 23:17:00 [ 1247.409119] kernel BUG at
drivers/md/bcache/buckets.c:505!
Mar 17 23:17:00 [ 1247.409149] invalid opcode: 0000 [#1] SMP
Mar 17 23:17:00 [ 1247.409176] Modules linked in:
Mar 17 23:17:00 netconsole
Mar 17 23:17:00 tun
[snip list of modules]
Marcin
[1] bcache format --compression_type=gzip --metadata_replicas=2
--data_checksum_type=crc64 --metadata_checksum_type=crc64 --tier=2
/dev/sde1 --tier=3 /dev/sdd1
prev parent reply other threads:[~2017-03-17 22:26 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
2017-03-17 22:06 ` Marcin
2017-03-17 22:26 ` Marcin [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=c63b4675d9f93acebad942c51d9c56f0@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