All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robby Nelson <robertb.nelson@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-integrity and bcache
Date: Tue, 21 May 2019 08:48:50 -0700	[thread overview]
Message-ID: <CALyFwfofNB6qOGmfmJQEHfWBkWfQH2Jn1vHsqDVzZq1R4FqSPA@mail.gmail.com> (raw)
In-Reply-To: <35f81966-d9e9-3b5d-39b6-455dfa24a899@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

Thank you for the input.

It sounds like bcache is no longer being worked on as the dev is spending
time on bcachefs instead. I considered dm-cache but it seems you can no
longer use lvm snapshots with it.

I will take a look at that mailing list, thank you.

Integrity at the cost of a little performance is fine with me in this
application.

Thanks,
Robby

On Mon, May 20, 2019 at 11:27 PM Milan Broz <gmazyland@gmail.com> wrote:

> On 20/05/2019 23:34, Robby Nelson wrote:
> > I was hoping to see if anyone had any experience with or warnings
> > about using mdadm raid 1 with dm-integrity as a backing device for a
> > bcache device. I apologize if this is a dumb question, I don't have a
> > great technical understanding of all these systems.
>
> Hi,
>
> in general, this combination should work (and several people try to use
> dm-integrity
> as a backing device for MD raid), but I see some issues that dmintegrity
> reveals in MD subsystem.
>
> I am not sure about stability of bcache, this project had maintenance
> issues
> in the past, I do not use it. There is also dm-cache (that is also somehow
> integrated
> in LVM), that is at least maintained by the same group of people as
> dm-integrity :)
>
> Anyway, I think a better list to ask is dm-devel@redhat-com, there are
> many people
> that use similar various storage stack combinations.
>
> I do not expect super-performance with dmintegrity it the stack (it will
> always slow
> down operation). If you see any stability issues, please report them to
> the list above.
>
> Thanks,
> Milan
>

[-- Attachment #2: Type: text/html, Size: 2038 bytes --]

      reply	other threads:[~2019-05-21 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 21:34 [dm-crypt] dm-integrity and bcache Robby Nelson
2019-05-21  6:27 ` Milan Broz
2019-05-21 15:48   ` Robby Nelson [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=CALyFwfofNB6qOGmfmJQEHfWBkWfQH2Jn1vHsqDVzZq1R4FqSPA@mail.gmail.com \
    --to=robertb.nelson@gmail.com \
    --cc=dm-crypt@saout.de \
    /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.