All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: kent.overstreet@gmail.com,
	Igor Pavlenko <ipavlenko.mail@gmail.com>,
	linux-bcache@vger.kernel.org
Subject: Re: bcache crashes at boot time
Date: Thu, 22 Jun 2017 12:24:05 +0100	[thread overview]
Message-ID: <874lv8tgdm.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1706220045190.17052@mail.ewheeler.net> (Eric Wheeler's message of "Thu, 22 Jun 2017 00:47:52 +0000 (UTC)")

On 22 Jun 2017, Eric Wheeler verbalised:
> The physical blocksize must be the same as the cachedev IIRC.  If 4k, use 
> -w 4k in make-bcache.  There's a thread somewhere discussing those 
> details.  

They are both 4096, and my make_bcache line was

make_bcache -B /dev/md/fast -C /dev/ssd2 --block 4096 --bucket 2M --data-offset $((2*30720))

which should be appropriate, I think? (This was my second attempt: I
came out with a number of unprintable words when I found that
make_bcache doesn't try to figure out an appropriate data offset when
used atop a RAID array, so the default options misalign the entire
thing.)

(Something I didn't make clear enough is that there there were several
successful restarts and remounts before the failed one.)

This is a writethrough cache, so it can't be a writeback problem (thank
goodness).

-- 
NULL && (void)

      reply	other threads:[~2017-06-22 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 12:38 bcache crashes at boot time Igor Pavlenko
2017-06-20 22:04 ` Eric Wheeler
2017-06-21 11:05   ` Nix
2017-06-21 17:10     ` Kai Krakow
2017-06-21 21:57       ` Nix
2017-06-22  0:47     ` Eric Wheeler
2017-06-22 11:24       ` Nix [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=874lv8tgdm.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=bcache@lists.ewheeler.net \
    --cc=ipavlenko.mail@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.