Could send|receive be extended to allow being interrupted and resumed later on?
Maybe at least when sending read-only snapshots?
I'd naively assume that for a read-only snapshot it's always the same that's being sent (well not really sure, if that's really the case, e.g. when block groups are balanced, defragged, etc.).
If so, INTerrupting the two could print out some information on how far it already went, which next time one could be feed into send as parameter, and it would continue from there.
The motivation for this feature request is, that send|receving very large subvolumes takes obviously quite long and one may want/need to pause that (e.g. I don't want to leave my laptop running for days, even while I'm away).
Hey.
From [0], where it got no attention:
Hey.
This goes along with #719.
Could
send|receivebe extended to allow being interrupted and resumed later on?Maybe at least when sending read-only snapshots?
I'd naively assume that for a read-only snapshot it's always the same that's being sent (well not really sure, if that's really the case, e.g. when block groups are balanced, defragged, etc.).
If so,
INTerrupting the two could print out some information on how far it already went, which next time one could be feed intosendas parameter, and it would continue from there.The motivation for this feature request is, that
send|recevingvery large subvolumes takes obviously quite long and one may want/need to pause that (e.g. I don't want to leave my laptop running for days, even while I'm away).Thanks, Chris.
[0] https://lore.kernel.org/linux-btrfs/6f340d377c584239a1b8d4236d404d708e61d968.camel@scientia.org/T/#u