Bug 2005929

Summary:	[RFE] incremental send/receive for thinp
Product:	[Community] LVM and device-mapper	Reporter:	J. Bruce Fields <bfields>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	Thin Provisioning	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, ajmitchell, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version:	unspecified	Keywords:	FutureFeature
Target Milestone:	---	Flags:	pm-rhel: lvm-technical-solution? pm-rhel: lvm-test-coverage?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description J. Bruce Fields 2021-09-20 13:55:55 UTC

We'd like to be able to snapshot a filesystem and distribute it over the network.

Subsequently we'd like to distribute later snapshots, with only the differences being transmitted.

Our goal is to use this to replicate read-only filesystems to multiple NFS servers, to improve reliability and aggregate bandwidth for rarely-changing data and to allow data to be moved closer to widely distributed clients.

For those purposes, it's best if NFS filehandles stay the same across replicas.  NFS filehandles depend on inode and generation numbers that aren't preserved by copying at the filesystem level, so we need either block-level or filesystem-specific tools.

thin_delta in device-mapper-persistent-data appears to be a start on this.