-by: Paul Lawrence
Cc: Alasdair Kergon
Cc: Mike Snitzer
Cc: dm-de...@redhat.com
Cc: Jonathan Corbet
Cc: Shaohua Li
Cc: linux-doc@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux-r...@vger.kernel.org
---
Documentation/device-mapper/dm-bow.txt | 103 +++
drivers/md/Kconfig
the device remains in the original state but the merge is complex.
On 10/23/2018 03:18 PM, Alasdair G Kergon wrote:
On Tue, Oct 23, 2018 at 02:23:28PM -0700, Paul Lawrence wrote:
It is planned to use this driver to enable restoration of a failed
update attempt on Android devices using ext4
kulas Patocka wrote:
On Wed, 24 Oct 2018, Paul Lawrence wrote:
Android has had the concept of A/B updates for since Android N, which means
that if an update is unable to boot for any reason three times, we revert to
the older system. However, if the failure occurs after the new system has
st
The concept intrigued me, so I actually went on to try your prototype.
I could apply it on v4.12 mainline (newer kernel versions introduce
changes in "struct bio" in "include/linux/blk_types.h" those don't let
the module compile – I think minor changes would be necessary to adapt
to the new str
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 thi