Linux bcache driver list
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: linux-bcache@vger.kernel.org
Subject: Tiering in bcachefs
Date: Mon, 12 Sep 2016 18:17:11 -0800	[thread overview]
Message-ID: <20160913021711.oxowdbp2sim5xwaq@kmo-pixel> (raw)

Just wrote a long post explaining all about tiering in bcachefs:

https://www.patreon.com/posts/all-about-6751413

Also, tiering should now be working! I'd appreciate help testing it.

Notes:

Chris Halse Rogers (RAOF in the #bcache IRC channel) has been testing it. He has
been seeing an intermittent deadlock while copying large amounts of data, which
may or may not be tiering related: if anyone else hits it, I'd really appreciate
if you could grab backtraces. Do a "echo t > /proc/sysrq-trigger" and then grab
the full dmesg log - that should be enough to figure out what the deadlock is.

I haven't gotten to device add/remove yet, don't try it - you'll need to create
a new filesystem:

bcache format --tier 0 <SSD> --tier 1 <HDD>

Also, if you've already been playing with tiering, I highly recommend you create
a new filesystem. One of the bugs was an issue with which pointers are
considered dirty - in an extent with a tier 0 pointer and a tier 1 pointer, the
tier 0 pointer was being considered dirty instead of the tier 1 pointer (with
predictably bad consequences; tier 0 would fill up because the tiering thread
wasn't actually making anything on tier 0 clean). On a fixed kernel, as extents
are migrated it'll end up fixing which pointers are considered dirty which may
or may not trigger assertions as which pointers are considered dirty changes.

                 reply	other threads:[~2016-09-13  2:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160913021711.oxowdbp2sim5xwaq@kmo-pixel \
    --to=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