public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Marcin <marcin@mejor.pl>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [bcachefs] problem with `bcache fsck`
Date: Thu, 16 Mar 2017 15:57:16 -0800	[thread overview]
Message-ID: <20170316235651.oehere2zxhewbbdh@moria.home.lan> (raw)
In-Reply-To: <f7e0b5acca043eff08a55f424470221d@mejor.pl>

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

> You have implemented too many features, everyone find something usefull for
> self and want to have it. You should implement only writing and reading
> to/from files;)

Heh :)

> Btw:
> # curl https://evilpiepirate.org/git/bcache-tools.git/
> curl: (51) SSL: no alternative certificate subject name matches target host
> name 'evilpiepirate.org'

Works for me now - I was updating SSL certs and some other stuff earlier
though, I might have broken it temporarily then

  reply	other threads:[~2017-03-17  0:05 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 [this message]
2017-03-17  8:57       ` Marcin
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=20170316235651.oehere2zxhewbbdh@moria.home.lan \
    --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