strange behavier after finished backup

2010-08-20 Thread baleareninsel
Hola,

new to the list and maybe having problems with english I ask for a friendly and 
a not too difficult answer.

Using Windows 7 Pro,
D-link DNS-323 NAS-Storage
rSync: actual Version (just downloaded)

Here is the stange behavier:
I use 
rsync.exe -a -v --progress --delete --ignore-errors --force /cygdrive/N/ 
/cygdrive/ //SPEICHER/Volume_1/Backup/10-er/D$/

So I want to backup the drive N from the Windows-Computer to 
//SPEICHER/Volume_1/Backup/10-er/D$/ on the NAS-Drive

That works fine until all files are copied from N to 
//SPEICHER/Volume_1/Backup/10-er/D$/

After finishing that rSync starts to coppy ALL Drives (c:,D:,E:,...) from the 
Windows system to the NAS-Drive //SPEICHER/Volume_1/Backup/10-er/D$/ which is, 
of course not, what I want :(

Well knowing, that the mistakeis mostly sitting in front of the screen, I ask 
your experianced eyes, if you see my mistake or have a helpfull idea.

Thanks and - sorry - for making mistakes with my english

Horst


---
 
Horst Peters 
C./Ladera 22-2
E-07750 Cala Galdana
Menorca / Spanien
Fon:+34-971- 15 45 62
Mobil: +34 971-15 45 62
 
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


RE: strange behavier after finished backup

2010-08-20 Thread Tony Abernethy
balearenin...@gmx.net wrote:
 
 Hola,
 
 new to the list and maybe having problems with english I ask for a
 friendly and a not too difficult answer.
 
 Using Windows 7 Pro,
 D-link DNS-323 NAS-Storage
 rSync: actual Version (just downloaded)
 
 Here is the stange behavier:
 I use
 rsync.exe -a -v --progress --delete --ignore-errors --force
 /cygdrive/N/ /cygdrive/ //SPEICHER/Volume_1/Backup/10-er/D$/

Assuming the above was all on one line:
Rsync.exe -a -v --progress --delete --ignore errors --force
/cygdrive/N/##-- this is the N drive
/cygdrive/  ##--  this is ALL the drives that cygwin can find
//SPEICHER/... ##--  this is the TARGET.  The above TWO parameters are sources.

 
 So I want to backup the drive N from the Windows-Computer to
 //SPEICHER/Volume_1/Backup/10-er/D$/ on the NAS-Drive
 
 That works fine until all files are copied from N to
 //SPEICHER/Volume_1/Backup/10-er/D$/
 
 After finishing that rSync starts to coppy ALL Drives (c:,D:,E:,...)
 from the Windows system to the NAS-Drive //SPEICHER/Volume_1/Backup/10-
 er/D$/ which is, of course not, what I want :(
This comes from the SECOND SOURCE PARAMETER /cygdrive/

 
 Well knowing, that the mistakeis mostly sitting in front of the screen,
 I ask your experianced eyes, if you see my mistake or have a helpfull
 idea.
 
 Thanks and - sorry - for making mistakes with my english
 
 Horst
 
 
 ---
 
 Horst Peters
 C./Ladera 22-2
 E-07750 Cala Galdana
 Menorca / Spanien
 Fon:+34-971- 15 45 62
 Mobil: +34 971-15 45 62
 
 --
 Please use reply-all for most replies to avoid omitting the mailing
 list.
 To unsubscribe or change options:
 https://lists.samba.org/mailman/listinfo/rsync
 Before posting, read: http://www.catb.org/~esr/faqs/smart-
 questions.html
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: RE: strange behavier after finished backup

2010-08-20 Thread baleareninsel
Verry fast answer... Thank you Tony


 
 Hola,
 
 new to the list and maybe having problems with english I ask for a
 friendly and a not too difficult answer.
 
 Using Windows 7 Pro,
 D-link DNS-323 NAS-Storage
 rSync: actual Version (just downloaded)
 
 Here is the stange behavier:
 I use
 rsync.exe -a -v --progress --delete --ignore-errors --force
 /cygdrive/N/ /cygdrive/ //SPEICHER/Volume_1/Backup/10-er/D$/

 Assuming the above was all on one line: 
YES!
 Rsync.exe -a -v --progress --delete --ignore errors --force
 /cygdrive/N/ ##-- this is the N drive ### the source
 /cygdrive/   ##--  this is ALL the drives that cygwin can find
 //SPEICHER/...  ##--  this is the TARGET.  The above TWO parameters are 
sources.

Why TWO parameters??? As I read I must use cygdrive under windows for each 
drive. (Source and target)

 
 So I want to backup the drive N from the Windows-Computer to
 //SPEICHER/Volume_1/Backup/10-er/D$/ on the NAS-Drive
 
 That works fine until all files are copied from N to
 //SPEICHER/Volume_1/Backup/10-er/D$/
 
 After finishing that rSync starts to coppy ALL Drives (c:,D:,E:,...)
 from the Windows system to the NAS-Drive //SPEICHER/Volume_1/Backup/10-
 er/D$/ which is, of course not, what I want :(

 This comes from the SECOND SOURCE PARAMETER /cygdrive/
H... and what to do delete the  SECOND SOURCE PARAMETER ?? Yust nou use the 
second /cygdrive/? 


 
 Well knowing, that the mistakeis mostly sitting in front of the screen,
 I ask your experianced eyes, if you see my mistake or have a helpfull
 idea.
 
 Thanks and - sorry - for making mistakes with my english
 
 Horst
 
 
 ---
 
 Horst Peters
 C./Ladera 22-2
 E-07750 Cala Galdana
 Menorca / Spanien
 Fon:+34-971- 15 45 62
 Mobil: +34 971-15 45 62
 
 --
 Please use reply-all for most replies to avoid omitting the mailing
 list.
 To unsubscribe or change options:
 https://lists.samba.org/mailman/listinfo/rsync
 Before posting, read: http://www.catb.org/~esr/faqs/smart-
 questions.html
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Check/compare modtime before deleting?

2010-08-20 Thread Chris
Thanks Matt.  I'll do some research on unison.

- Chris

On Thu, Aug 19, 2010 at 8:27 PM, Matt McCutchen m...@mattmccutchen.net wrote:
 On Thu, 2010-08-19 at 11:31 -0700, Chris wrote:
 I need to keep two identical copies of files on my desktop and laptop,
 so I want to use the -delete option.  But I don't want to delete files
 that are created after last sync.  Is there a way to keep files with
 modtime later than a file of a different name (a flag file created
 before each sync) when using the -delete option?

 No.  As soon as you have one side making arbitrary changes that you
 don't want to clobber, you need a stateful change-propagation tool such
 as unison (http://www.cis.upenn.edu/~bcpierce/unison/).

 --
 Matt


-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


rsync: pack_smb_acl: sys_acl_init(): Cannot allocate memory

2010-08-20 Thread Mike Bombich
Before I call this a bug, I figured I'd ask -- what's the + 3 for in 
calc_sacl_entries?  

static int calc_sacl_entries(const rsync_acl *racl)
{
/* A System ACL always gets user/group/other permission entries. */
return racl-names.count
#ifdef ACLS_NEED_MASK
 + 4;
#else
 + (racl-mask_obj != NO_ENTRY) + 3;   What's this for?
#endif
}


On Mac OS X, a file with the system limit of 128 ACEs will consistently run 
into the error noted in the subject.  calc_sacl_entries is returning 131 for 
such a file, and acl_init() returns ENOMEM as a result.  If I remove the + 3, 
everything is peachy -- all the ACEs are copied and I don't see any harm.  Is 
there an unforeseen consequence to removing the +3?

This script reliably reproduces the error:

##
#!/bin/sh

rsync=/usr/local/bin/rsync

src=`mktemp -d /tmp/src.XX`
tgt=`mktemp -d /tmp/tgt.XX`
echo $tgt/test
file=$src/test
touch $file

x=0
limit=128
while [ $x -lt $limit ] ; do
 chmod +a# $x $USER allow write,writeattr,writeextattr $file
 x=$(($x + 1))
done

$rsync -vaAX $src/ $tgt/

rm -rf $src $tgt
##


Thanks,
Mike
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: IO error causing file deletion failure?

2010-08-20 Thread Morgan Read
On 15/08/10 14:06, Morgan Read wrote:
 On 09/08/10 09:32, Matt McCutchen wrote:
 On Sat, 2010-08-07 at 19:54 +1200, Morgan Read wrote:
 I've been running this command, with the accompanying error:
 [r...@mythtv ~]# ssh -t rs...@192.168.1.40 sudo rsync -avzAXH
 --delete-after -e /home/rsync/bin/rsync_ssh /home/

 building file list ... rsync: readlink_stat(/home/morgan/.gvfs)
 failed: Permission denied (13)

 Yes, gvfs-fuse mounts a FUSE filesystem (which denies access to root by
 default) in an unwise place.

 https://encrypted.google.com/search?q=gvfs+rsync

 https://bugzilla.gnome.org/show_bug.cgi?id=560658

 You'll need to exclude /home/*/.gvfs .

 IO error encountered -- skipping file deletion

 If anyone is able shed some light on either the error or why it might
 prevent deleting files I could save on harddrives:)

 From the man page description of --delete

 If the sending side detects any I/O errors, then the deletion of
 any files at the destination will be automatically disabled.
 This is to prevent temporary filesystem failures (such as NFS
 errors) on the sending side from causing a massive deletion of
 files on the  destination.   You can override this with the
 --ignore-errors option.

 Matt  Henri thank you for following up.
 
 I've never worried about .gvfs because I knew it was only part of the
 mount system for gnome virtual file system (fuse).  It always threw
 errors, but I've never noticed that preventing deletion.  (Perhaps I've
 just never noticed...)  I'll fix that and see if skipping file deletion
 gets fixed in the process.
 
 Will report back, many thanks.
 M.
 
Yup, all good on taking out /home/*/.gvfs.  Guess I only missed that
before as I was on an old system and had a flood of other errors related
to extended attributes etc.  Now, after much hd thrashing, my b/u is
substantially smaller...

(OT, that .gvfs is really a complete stuff up, other than the problems
above, it doesn't mount my vfat iso with long file names, only the
truncated dos one - meaning I have to mount my IPLS.iso with sudo mount
-o loop IPLS.iso /mnt/cdrom anyway - go figure...  Note to self, must
file another bug report...)

Many thanks all.  (Henri, I'm in Auckland - but my brothers in ChCh if
that lessens the pain any:)

Regards,
Morgan.
-- 
Morgan Read
NEW ZEALAND
mailto:mstuffATreadDOTorgDOTnz
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html