From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Randy Dunlap <rdunlap@infradead.org>, <axboe@kernel.dk>,
<hch@infradead.org>, <corbet@lwn.net>, <snitzer@kernel.org>
Cc: <viro@zeniv.linux.org.uk>, <brauner@kernel.org>,
<willy@infradead.org>, <dlemoal@kernel.org>, <wsa@kernel.org>,
<heikki.krogerus@linux.intel.com>, <ming.lei@redhat.com>,
<gregkh@linuxfoundation.org>, <linux-block@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v4 11/11] blksnap: Kconfig and Makefile
Date: Tue, 13 Jun 2023 12:47:29 +0200 [thread overview]
Message-ID: <7dbbaf60-c85d-5a7a-8f16-5f5e4ff43cd8@veeam.com> (raw)
In-Reply-To: <499ded51-3fb8-f11b-8776-08ab2e9a8812@infradead.org>
On 6/13/23 01:43, Randy Dunlap wrote:
>> +config BLKSNAP
>> + tristate "Block Devices Snapshots Module (blksnap)"
>> + help
>> + Allow to create snapshots and track block changes for block devices.
>> + Designed for creating backups for simple block devices. Snapshots are
>> + temporary and are released then backup is completed. Change block
> when backup is completed.
>
> or is the order of operations as listed: release snapshots and then backup
> can be completed?
>
>> + tracking allows to create incremental or differential backups.
"when backup is completed." - it will be more correct.
Normal backup process:
Take snapshot Release snapshot
| Start backup Finish backup |
| | Copy data from snapshot images | |
------------------------------------------------------------------------->
t
In case of failure, for example, when the snapshot is overflowing:
The snapshot is corrupted
Take snapshot | Release snapshot
| Start backup | | Finish failed backup
| | Copy data from snapshot images | | |
------------------------------------------------------------------------->
t
next prev parent reply other threads:[~2023-06-13 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:58 [PATCH v4 01/11] documentation: Block Device Filtering Mechanism Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 02/11] block: " Sergei Shtepa
2023-06-13 1:51 ` Randy Dunlap
2023-06-13 12:34 ` Sergei Shtepa
2023-06-13 14:16 ` Randy Dunlap
2023-06-09 11:58 ` [PATCH v4 03/11] documentation: Block Devices Snapshots Module Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 04/11] blksnap: header file of the module interface Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 05/11] blksnap: module management interface functions Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 06/11] blksnap: handling and tracking I/O units Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 07/11] blksnap: minimum data storage unit of the original block device Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 08/11] blksnap: difference storage Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 09/11] blksnap: event queue from the " Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 10/11] blksnap: snapshot and snapshot image block device Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 11/11] blksnap: Kconfig and Makefile Sergei Shtepa
2023-06-12 23:43 ` Randy Dunlap
2023-06-13 10:47 ` Sergei Shtepa [this message]
2023-06-13 1:52 ` [PATCH v4 01/11] documentation: Block Device Filtering Mechanism Randy Dunlap
2023-06-13 15:23 ` Sergei Shtepa
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=7dbbaf60-c85d-5a7a-8f16-5f5e4ff43cd8@veeam.com \
--to=sergei.shtepa@veeam.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dlemoal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=rdunlap@infradead.org \
--cc=snitzer@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=wsa@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
all inboxes | Powered by JetHome®