On Tue, 2015-11-24 at 21:27 +0000, Hugo Mills wrote: > -p only sends the file metadata for the changes from the reference > snapshot to the sent snapshot. -c sends all the file metadata, but > will preserve the reflinks between the sent snapshot and the (one or > more) reference snapshots. Let me see if I got that right: - -p sends just the differences, for both data and meta-data. - Plus, -c sends *all* the metadata, you said... but will it send all data (and simply ignore what's already there) or will it also just send the differences in terms of data? - So that means effectively I'll end up with the same... right?
In other words, -p should be a tiny bit faster... but not that extremely much (unless I have tons[0] of metadata changes) > You can only use one -p (because there's > only one difference you can compute at any one time), but you can use > as many -c as you like (because you can share extents with any number > of subvols). So that means, if it would work correctly, -p would be the right choice for me, as I never have multiple snapshots that I need to draw my relinks from, right? > In implementation terms, on the receiver, -p takes a (writable) > snapshot of the reference subvol, and modifies it according to the > stream data. -c makes a new empty subvol, and populates it from > scratch, using the reflink ioctl to use data which is known to exist > in the reference subvols. I see... I think the manpage needs more information like this... :) Thanks, for you help :-) Chris. [0] People may argue that one has XXbytes of metadata, and tons are a measurement of weight... but when I recently carried 4 of the 8TB HDDs in my back... I came to the conclusion that data correlates to gram ;-)
smime.p7s
Description: S/MIME cryptographic signature