Matthew Dillon <dil...@apollo.backplane.com> writes: > > It could have caught the rsync in the middle, though it isn't supposed > to break inode<->file linkages. rsync might be re-creating the hardlinks > on every pass.
rsync is running right before the snapshots are being created, so rsync itself had already exited (however it didn't sync or sleep in betweeen) > > Are the other snapshots ok? they are fine. > > The most reliable way is to create a manual snapshot as part of your > rsync script so the snapshot occurs on a quiescent filesystem. Something > like this: > > do rsync stuff > sync; sleep 5; sync; sleep 5; sync; sleep 5 > hammer snapshot /backup/sync /var/hammer/backup/sync "rsync snapshot" I do that now and will watch for similar problems. Thanks for your help. -- Cheers Ralf
