public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin <marcin@mejor.pl>
To: linux-bcache@vger.kernel.org
Subject: [bcachefs] problem with `bcache fsck`
Date: Thu, 16 Mar 2017 16:16:29 +0100	[thread overview]
Message-ID: <6aaaad468dd77840265bcd9f31f1878a@mejor.pl> (raw)

Hi!
It's good to hear that silence on mailinglist doesn't mean that there is 
no changes in developing bcachefs!

I found some problems with bcache tools.
bcache fsck errors:

a) if I creat4e filesystem and run fsck before first mount I'm getting:
# bcache fsck /dev/sdd1
initializing new filesystem
error opening /dev/sdd1: cannot allocate new btree root

b) After first mount%umount fsck still doesn't work:
# bcache fsck /dev/sdd1
no journal entries found
filesystem contains errors, but repair impossible
error opening /dev/sdd1: fsck error

bcachefs-tools at commit d4e6736e59c96

Is bcache fsck able to do fsck on tiered devices?
I know that there is some stability problem with tiered devices because 
when I mounted tiered fs and started to copy files on it the host 
rebooted after some time. I have to run netconsole to catch what kernel 
says, then I post it on ML.

And I'm still missing compression saves free space on disk:)

Marcin

             reply	other threads:[~2017-03-16 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 15:16 Marcin [this message]
2017-03-16 20:34 ` [bcachefs] problem with `bcache fsck` 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

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=6aaaad468dd77840265bcd9f31f1878a@mejor.pl \
    --to=marcin@mejor.pl \
    --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