From: Bart Van Assche <bvanassche@acm.org>
To: Sergei Shtepa <sergei.shtepa@veeam.com>, Jens Axboe <axboe@kernel.dk>
Cc: "masahiroy@kernel.org" <masahiroy@kernel.org>,
"michal.lkml@markovi.net" <michal.lkml@markovi.net>,
"koct9i@gmail.com" <koct9i@gmail.com>,
"jack@suse.cz" <jack@suse.cz>,
"damien.lemoal@wdc.com" <damien.lemoal@wdc.com>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"steve@sk2.org" <steve@sk2.org>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 0/1] block io layer filters api
Date: Tue, 1 Sep 2020 08:34:17 -0700 [thread overview]
Message-ID: <b99a1577-6f39-9228-d176-5a8bc38bd64d@acm.org> (raw)
In-Reply-To: <20200901132957.GA18251@veeam.com>
On 2020-09-01 06:29, Sergei Shtepa wrote:
> However, the same time requirement also presents a big immediate problem -
> as until this is done, over a hundred thousands of Linux users will not be
> able to protect their servers running the impacted kernels
> (our backup agent is free).
> They will be forced to stop using the new version of the kernel
> (or take a risk of data loss).
How can backup software work at the block layer level without any cooperation
of higher layers? How is it e.g. guaranteed that backups are crash-consistent?
What happens if the network connection with the backup server is lost? How
much time is needed to recover after the network connection has been restored?
Does the contents of the entire block device has to be resent to the backup
server?
Thanks,
Bart.
prev parent reply other threads:[~2020-09-01 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 19:13 Sergei Shtepa
2020-08-27 19:13 ` [PATCH 1/1] " Sergei Shtepa
2020-08-28 7:24 ` [PATCH 0/1] " Damien Le Moal
2020-08-28 13:54 ` Jens Axboe
2020-09-01 13:29 ` Sergei Shtepa
2020-09-01 14:49 ` Jens Axboe
2020-09-01 16:35 ` Sergei Shtepa
2020-09-01 15:34 ` Bart Van Assche [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=b99a1577-6f39-9228-d176-5a8bc38bd64d@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=jack@suse.cz \
--cc=koct9i@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ming.lei@redhat.com \
--cc=sergei.shtepa@veeam.com \
--cc=steve@sk2.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®