Mailinglist Archive: opensuse (2576 mails)
|< Previous||Next >|
Re: [opensuse] backups via rsync leaving old junk in the backup?
- From: "Brian K. White" <brian@xxxxxxxxx>
- Date: Wed, 18 Feb 2009 19:46:54 -0500
- Message-id: <4D0D9DEEC0C14AB7B4253C687C683F01@miata>
----- Original Message ----- From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
Cc: "opensuse" <opensuse@xxxxxxxxxxxx>
Sent: Wednesday, February 18, 2009 6:20 PM
Subject: Re: [opensuse] backups via rsync leaving old junk in the backup?
On Wed, Feb 18, 2009 at 6:15 PM, Boris Epstein <borepstein@xxxxxxxxx> wrote:On Wed, Feb 18, 2009 at 6:08 PM, Greg Freemyer <greg.freemyer@xxxxxxxxx> wrote:The --delete-after flag is supposed to delete files from the dest notAll,I believe rsync is not designed to remove anything in the destination directory.
I just noticed that the main directory is 247GB, but the remote copy is 354GB.
I assume rsync can cause the extra files on the remote to be deleted?
I'm currently using:
rsync -avh --delete-after --stats --links --partial-dir=<transfer_dir>
--timeout=1800 <BACKUP_DIR> <remote_user>@<remote_server>/<remote_dir>
present in the source. (or so I believe.)
I don't remember really testing this flags use before, so maybe I
don't understand what it actually does?
I use --del and --delete-excluded _all_ the time and I assure you they delete things from the target.
If they didn't I'd have big problems. Deleting stuff is just as important as anything else when it comes to maintaining an accurate and consistent copy of a dataset.
I would look at:
1) Does the rsync job actually finish without errors or warnings, and without being killed while in progress?
2) Are there multiple rsync's running from previous days? (probably not since the timeout should be preventing exactly this, however...)
3) Is the timeout causing it to die before ending? In other words, before ever reaching the point where it would have performed the --delete-after. Take out --delete-after and juste use --del, or, increase the timeout, or even temporarily remove the timeout.
4) Do the filesystems on each side report space usage the same way? As in, are they the same kind of filesystem? Are they on the same kind of hardware platform? Were they created using the same blocking factors?
5) Are there processes on the target machine possibly holding hidden file handles open? As in, when a process has a file handle, and you delete the file, the file isn't really deleted until any such handles are released. However, it looks deleted to casual inspection. No new process can access it and it isn't shown anywhere except lsof/lslk output and indirect things like, you guessed it, mystery du/df discrepencies.
I think #3 is most likely.
Brian K. White brian@xxxxxxxxx http://profile.to/KEYofR
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
|< Previous||Next >|