Here is the missing attachment ;-)
On Fri, 2023-09-22 at 21:01 +0200, rsync--- via rsync wrote:
> On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote:
> > So I decided to do a quick test using the Linux kernel source tree since
> > it has lots of files.
>
> Excellent idea using kernel sources!
On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote:
> So I decided to do a quick test using the Linux kernel source tree since
> it has lots of files.
Excellent idea using kernel sources! A lot of different files...
I will use this to create indicative benchmarks for different scenarios...
>
On Fri 22 Sep 2023, Kevin Korb via rsync wrote:
> 444 {} +' to make read only files for rsync to want to chmod, then used cp
> -al to make several duplicate trees using hard linked files. An rm -rf on
> one such tree took .97 seconds while an rsync deletion took 1.25 seconds.
Be sure to drop the
So I decided to do a quick test using the Linux kernel source tree since
it has lots of files. I duplicated a tree, used 'find . -type f -exec
chmod 444 {} +' to make read only files for rsync to want to chmod, then
used cp -al to make several duplicate trees using hard linked files. An
rm -r
On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote:
> I have heard in the past that rsyncing an empty dir over a tree to
> delete the tree is faster than an rm -rf but I can't say I have ever
> benchmarked it to get any actual numbers.
This **may** indeed be a myth (for a long time n
I had intended to come back to this but because I didn't really think I
had anything to add to the discussion I put it at a low enough priority
that I forgot about it. But I saw your bug report and was surprised to
see that I was already unhelpful on this topic but because that original
poster
On 16.04.2015 12:20, ? ?? wrote:
> Hi, Rsync.
>
> find /home/rc-41/data/061/2015-04-01-07-04/ -delete
> I know not suitable
-mindepth 1 ?
That deletes the whole contents, but doesn't delete the folder itself.
--
Matthias
--
Please use reply-all for most replies to avoid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought of something else if it must be rsync that is used...
rsync -a --delete --exclude='*' --delete-excluded /anywhere/
/stuff/to/delete/
That would empty the target dir regardless of what is in the source dir.
I would still like to hear how th
problem is he's trying to rsync into the target dir and have the
side effect of delete. so an empty dir would necessarily need to be
in the target of course and thus created there, triggering the quota block.
he tried to avoid this by using device files then 'blocking all device files'
but i think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't understand what is wrong with rm either.
But if you must have an empty directory is there a tmpfs where you can
make one? Is there already an empty one like /var/empty?
On 04/16/2015 10:13 AM, Ken Chase wrote:
> Wow, it took me a few seconds
Wow, it took me a few seconds to figure out what you were trying to do.
What's wrong with rm?
Also I think trying to leverage the side of disqualifying all source files
just to get the delete effect (very clever but somewhat obtuse!) risks
creating a temporary file of some kind in the target at t
Hi,
I think a very similar functionality can be achieved by using the existing
--backup option? Using the backup (-b) option in conjunction with the --del
option allows you to set a suffix (using --suffix) . But of course you
can't add a prefix (to hide it) currently I think
So I might use somethin
At 22:02 28.01.2013 +, Stewart Jeacocke wrote:
>Hi,
>
>I'm trying to copy some directories with rsync and would like to
>delete files from the destination if they no longer exist in the
>source.
>
>I'm using the following command:
>
>rsync -v --archive --hard-links --delete --force
>--filter=':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there any output? How about with an additional -v ?
Is there a .rsync-filter file anywhere?
On 01/28/13 17:02, Stewart Jeacocke wrote:
> Hi,
>
> I'm trying to copy some directories with rsync and would like to
> delete files from the destinatio
On Mon, 2009-05-18 at 02:28 -0700, tammy wrote:
> I have 3 load balancing servers. Each user may login to different servers to
> upload their data, lets say, a company logo.
> That's why i tried to use rsync to synchronize the uploaded logo and some
> other necessary modules. This mean, each server
Peter Daum wrote:
- The problem only occurs when there is more than 1 file system to
sync. When I only backup "/", everything is fine, when I add another
source file system, nothing below "/var" will be deleted (I still don't
have a clue, why this occurs on "/var" but not on other paths)
Hi,
I still couldn't find a really simple test case but at least I can
provide some more details regarding this obscure issue:
- The problem only occurs when there is more than 1 file system to
sync. When I only backup "/", everything is fine, when I add another
source file system, nothing b
Hi,
Izidor Jerebic wrote:
Are there any errors while doing the rsync?
I have recently discovered that to create identical copy on mac os x (in
the presence of any errors), you need to additionally specify
--ignore-errors and --force-delete, otherwise nothing will be deleted
(it seems that
Hello, Peter,
Are there any errors while doing the rsync?
I have recently discovered that to create identical copy on mac os x
(in the presence of any errors), you need to additionally specify --
ignore-errors and --force-delete, otherwise nothing will be deleted
(it seems that as soon as
On Wed, 2008-08-20 at 00:20 +0200, Komáromi Tamás wrote:
> I would like to sync my Linux firewall to my Mac OS X.
> The rsync deletes my files with accents and download it again.
> $ /sw/bin/rsync --archive --update --verbose --delete firewall:teszt .
> receiving incremental file list
> deleting
I see, you're right :)
Is there anything useful that can be donated to the rsync developers?
Keep up the great work.
Best regards,
Tiago Marques
On Sun, Aug 10, 2008 at 11:16 PM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Sun, 2008-08-10 at 23:04 +0100, Tiago Marque
On Sun, 2008-08-10 at 23:04 +0100, Tiago Marques wrote:
> It worked, --delete-excluded was all that was missing.
> I really think this should be the implied behavior and would like to
> see it as default, if there really isn't a good reason for it being
> this way.
The current behavior is useful i
Thanks! It worked, --delete-excluded was all that was missing.
I really think this should be the implied behavior and would like to
see it as default, if there really isn't a good reason for it being
this way.
Best regards,
Tiago Marques
On Sun, Jul 13, 2008 at 6:26 P
On Tue, 2008-07-29 at 12:10 -0400, Matt McCutchen wrote:
> You are welcome to request an option to make rsync delete destination
> files that are matched in --compare-dest dirs. I would actually suggest
> a more general option called --recheck-basis-dirs that also replaces a
> destination file mat
On Tue, 2008-07-29 at 17:19 +0200, Gabriel CORRE wrote:
> I'm trying to do a differential backup. Each commands/scripts are launch on
> backup server side.
>
> - rsync-ref: 1 script perform a complete backup to a directory "ref".
>something like that:
> rsync --archives \
>statio
Rsync 2.6.9 seems to think that the destination is already up to date.
What do you expect it to do that it isn't doing? Update an existing
file? (What are the size and mtime of that file and the corresponding
source file?) Delete an extraneous file? (Note that you'll have to
convert the exclude
On Sat, 2008-07-12 at 03:48 +0100, Tiago Marques wrote:
> Hmm, looks like I'm not done with this, yet.
> With rsync 3.02, it works fine:
>
> rsync --exclude='/*/' --delete-before -tvlpr
> rsync://rsync.sabayonlinux.org/SabayonLinux/ /storage/mirrors/
>
> But not with the 2.6.9 version :|
> I just
Hmm, looks like I'm not done with this, yet.
With rsync 3.02, it works fine:
rsync --exclude='/*/' --delete-before -tvlpr
rsync://rsync.sabayonlinux.org/SabayonLinux/ /storage/mirrors/
But not with the 2.6.9 version :|
I just get this, with the mirror completely outdated:
receiving
Indeed, that worked great for me!
Big thanks to both for your time.
Tiago Marques
On 7/11/08, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-07-11 at 13:01 -0700, Wayne Davison wrote:
> > On Fri, Jul 11, 2008 at 04:22:04PM +0100, Tiago Marques wrote:
> > > I was already
On Fri, 2008-07-11 at 13:01 -0700, Wayne Davison wrote:
> On Fri, Jul 11, 2008 at 04:22:04PM +0100, Tiago Marques wrote:
> > I was already using the -d option, it download the subdirs also.
>
> You also need to not use -r (e.g. either expand -a and omit -r, or
> specify --no-r).
-d will create th
On Fri, Jul 11, 2008 at 04:22:04PM +0100, Tiago Marques wrote:
> I was already using the -d option, it download the subdirs also.
You also need to not use -r (e.g. either expand -a and omit -r, or
specify --no-r).
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing l
I was already using the -d option, it download the subdirs also.
The --exclude option worked fine though, and --delete-before is now
working very well.
Tks to all!
Best regards,
Tiago Marques
On Fri, Jul 4, 2008 at 11:18 PM, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On F
On Fri, Jul 04, 2008 at 05:08:41PM -0400, Matt McCutchen wrote:
> Use --recursive and then exclude the stuff you don't want, e.g.,
> --exclude='/*/' to exclude all subdirectories.
You can also use -d (--dirs) instead of -r (--recursive). That makes
rsync transfer just the contents of a specified
On Fri, 2008-07-04 at 20:11 +0100, Tiago Marques wrote:
> In the past, since
> --delete-before did nothing, I did a dry run and then parsed the
> output to have it "rm" the files that were to be deleted. That so also
> because the --delete needs the --recursive option, which for me is
> very imprac
On Fri, Jul 04, 2008 at 08:11:36PM +0100, Tiago Marques wrote:
> rsync --delete-before -v -tvlpr
> rsync://rsync.sabayonlinux.org/SabayonLinux/* ./ --dry-run
Check out the manpage on the --delete option. The very first paragraph
tells you why you shouldn't be using a wildcard (*) there:
ht
Inside the target dir, there is a file named "asdasdasd" which isn't
deleted, nor mentioned to, since this is a dry-run.
with:
rsync --delete-before -v -tvlpr
rsync://rsync.sabayonlinux.org/SabayonLinux/* ./ --dry-run
i get:
-
On Fri, 2008-07-04 at 16:13 +0100, Tiago Marques wrote:
> I had this working on an older version, since 2.6.9 that when I set
> --delete and --dry-run, I get no "Deleting **" lines.
Be sure to pass -v because, since rsync 2.6.7, --dry-run no longer
implies it:
http://gitweb.samba.org/?p=rsync
On Tue, Jun 10, 2008 at 03:03:23AM -0700, GiveMF wrote:
> So I want to sync from the dev directory (which doesn't have .svn
> directories) to one that does.
An exclude does two things: it prevents files that match from being
transferred from the sender, and it protects files that match from being
Seams I have sorted out my problem until futher.
By doing rsync over SSH to my NAS drive instead of mapping my NAS drive
using smbmount, --delete works fine.
/Torben
> For some time I have been using rsync to backup data between different
> machines and my NAS drive.
>
> But within the last 2 da
On Sun, 2007-11-04 at 13:50 -0800, Jesse Thompson wrote:
> What would be the closest approximation to something like this?
>
> # rsync -r --just-nuke-the-target remote::volume/directory
>
> Is it something that can be done with rsync?
Yes, but it is a bit awkward because rsync considers deletio
On 8/25/07, Ameerov <[EMAIL PROTECTED]> wrote:
> Hi, I hope this is the right place to post this... I came across this
> old unsolved post that is describing the exact problem i am having,
> tried emailing the author but the email bounced.
>
> http://lists.samba.org/archive/rsync/2006-June/015697.
On 5/5/07, Matthias Schniedermeyer <[EMAIL PROTECTED]> wrote:
If you have subdirectories to be killed:
find . -type d -empty -exec rmdir {}\;
You have to run that a few times (One time for each deepth-level), and don't
worry about the 'No such file or directory' warnings that it will spit for
e
Erik Red wrote:
> Hi,
>
> I made the mistake of doing an rsync of a directory into the wrong
> destination,
> so that the destination became a mix of two directories of unrelated files.
>
> Top unravel the mess, I could need something like a --delete-existing
> option.
>
> The semantics would be
I managed to solve this in the end.
It was file permissions. I had originally copied all the data across by
restoring from Backup tape and then started using Rsync to keep the two
identical.
After deleting the directories in question and rsyncing them from
scratch, the problem has been solved.
On Mon, Jun 05, 2006 at 08:19:24AM -0500, Smemoe, Richard L. wrote:
> It looks like it's only copying the changes to the original filesystem
> since the last rsync.
That's not very likely to be what is happening. I'd suggest using the
-v option so that you can see what rsync is deleting -- this s
lete-during
/production/filesystem/ .', but this gave me nothing in my backup
filesystem.
Thanks,
Richard
-Original Message-
From: Wayne Davison [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 11:37 AM
To: Smemoe, Richard L.
Cc: rsync@lists.samba.org
Subject: Re: rsync --
On Thu, Jun 01, 2006 at 09:31:49AM -0500, Smemoe, Richard L. wrote:
> When I added the -delete option, my backup started taking about two
> days to finish.
You'd be better off using --del (--delete-during) than --delete, as
it doesn't require a separate scan through the destination hierarchy.
Al
On Mon, 22 Jul 2002, Edward Farrar wrote:
> Rsync 2.5.5 is producing this error message and a core file when executing the
> command "/usr/local/bin/rsync -av --delete --force /net/OSCM/OS_ATLAS2/CONFIG/.
> /net/OSCM/OS_TITAN1/2.6/CONFIG/. /OS/2.6/CONFIG"
>
> building file list ... done
> rsync:
2002 13:25:54 -0700 (PDT)
To: g dm <[EMAIL PROTECTED]>
Subject: Re: Rsync --delete does not work
> On Tue, 23 Jul 2002, g dm wrote:
> > rsync -a --delete * /data/exp_dir
> > So, what did I do wrong?
>
> You're sending a list of files, not a directory (since '
- Original Message -
From: Wayne Davison <[EMAIL PROTECTED]>
Date: Tue, 23 Jul 2002 13:25:54 -0700 (PDT)
To: g dm <[EMAIL PROTECTED]>
Subject: Re: Rsync --delete does not work
> On Tue, 23 Jul 2002, g dm wrote:
> > rsync -a --delete * /data/exp_dir
> &
On Tue, 23 Jul 2002, g dm wrote:
> rsync -a --delete * /data/exp_dir
> So, what did I do wrong?
You're sending a list of files, not a directory (since '*' is expanded
by the shell into a list of files). The --delete option only works on
a directory-to-directory transfer, so try using this instea
Try adding -v to your rsync command to get more verbose output, perhaps
giving you an idea why --delete is not working as expected. --delete works
for me, but there are situations where rsync will ignore --delete for safety
(such as if certain errors occur).
Also, remember that "*" is expanded b
Thanks for the response. I'm not a programmer, so I'm struggling with your
request. But, I was able to produce the output below. Please let me know if
this helps. I tried to reproduce the problem on a smaller scale using tmp
files, but I was unsuccessful. I'll keep trying to come up with a sm
That's not enough information for us to be able to do anything with.
Can you at least find a stack backtrace in the core file? If you could
boil it down into something that someone else could reproduce that would
help a lot.
- Dave Dykstra
On Mon, Jul 22, 2002 at 07:19:26AM -0400, Edward Farrar
54 matches
Mail list logo
