From: Paul Lawrence <firstname.lastname@example.org>
To: Mikulas Patocka <email@example.com>
Cc: Alasdair Kergon <firstname.lastname@example.org>,
Mike Snitzer <email@example.com>,
Jonathan Corbet <firstname.lastname@example.org>,
Shaohua Li <email@example.com>
Subject: Re: [dm-devel] [RFC] dm-bow working prototype
Date: Mon, 29 Oct 2018 09:51:48 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> The snapshot target could be hacked so that it remembers space trimmed
> with REQ_OP_DISCARD and won't reallocate these blocks.
> But I suspect that running discard over the whole device would degrade
> performance more than copying some unneeded data.
> How much data do you intend to backup with this solution?
We are space-constrained - we will have to free up space for the backup
before we apply the update, so we have to predict the size and keeping
usage as low as possible is thus very important.
Also, we've discussed the resizing requirement of the dm-snap solution
and that part is not attractive at all - it seems it would be impossible
to guarantee that the resizing happens in a timely fashion during the
(very busy) update cycle.
Thanks everyone for the insights, especially into how dm-snap works,
which I hadn't fully appreciated. At the moment, and for the above
reasons, we intend to continue with the dm-bow solution, but do want to
keep this discussion open. If anyone is going to be at Linux Plumbers,
I'll be presenting this work and would love to chat about it more.
next prev parent reply other threads:[~2018-10-29 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:23 [RFC] dm-bow working prototype Paul Lawrence
2018-10-23 22:18 ` Alasdair G Kergon
2018-10-24 18:42 ` Paul Lawrence
2018-10-24 19:24 ` [dm-devel] " Mikulas Patocka
2018-10-25 0:01 ` Alasdair G Kergon
2018-10-25 10:20 ` Bryn M. Reeves
2018-10-25 17:23 ` Paul Lawrence
2018-10-26 20:03 ` Mikulas Patocka
2018-10-29 16:51 ` Paul Lawrence [this message]
2018-11-15 23:15 ` Mikulas Patocka
2018-12-02 10:07 ` Sandeep Patil
2018-10-25 16:30 ` MegaBrutal
2018-10-25 18:13 ` Paul Lawrence
2018-10-25 21:15 ` Wols Lists
2018-10-25 21:43 ` [dm-devel] " Darrick J. Wong
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).