Re: Windows 2003 Cygwin Netapp remote filesystem

2008-12-26 Thread Michael Chletsos
Ok so I have figured out the problem with my rsync daemon is the fact
that rsync interprets // as / and therefore is not seeing this as a
unc path, but rather a absolute path.

and /cygdrive/h does not work because it is not setup outside of the
cygwin environment, i.e. a windows service.

I could add it to the registry for cygwin mount points, but I think a
fix to the code might be better.

Any suggestions in the source, where this // problem might live?

On Tue, Dec 23, 2008 at 3:23 PM, Matt McCutchen m...@mattmccutchen.net wrote:
 Michael, please CC rsync@lists.samba.org so that others can help you and
 your messages are archived for others' future benefit.

 On Tue, 2008-12-23 at 14:02 -0700, Michael Chletsos wrote:
 thanks, I have perms, since I can read and write to the dir.

 Is the daemon running as the same user who you verified to have
 permission?  (If you have it installed as a service, it might run as a
 different user.  Again, I'm not familiar with the details, but the
 cwRsync people probably are.)

 Error message :

  chdir /cygdrive/h/test_rsync failed

 That should have been followed by a strerror message describing the
 failure, on the same line.  Please post the entire line.

 --
 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


Re: Windows 2003 Cygwin Netapp remote filesystem

2008-12-26 Thread Jamie Lokier
Michael Chletsos wrote:
 Ok so I have figured out the problem with my rsync daemon is the fact
 that rsync interprets // as / and therefore is not seeing this as a
 unc path, but rather a absolute path.
 
 and /cygdrive/h does not work because it is not setup outside of the
 cygwin environment, i.e. a windows service.

Even though it's a windows service, it does have the cygwin
environment.  E.g. /cygdrive/c should still work.

I've seen a similar problem with other cygwin programs running as
services.  E.g. the OpenSSH server, running as a windows service - you
log in over SSH, but can't access network shares from that session.
People have described workarounds for the OpenSSH problem, but none
looked simple or worked in every situation.

 I could add it to the registry for cygwin mount points, but I think a
 fix to the code might be better.

You might try that first, because it might not work, and then you'll
know if there is any point trying to get // passed directly.

-- Jamie
-- 
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


open solaris --one-file-system ignored, source path also ignored

2008-12-26 Thread Jesse Reynolds

Hello

I am attempting to backup a remote OpenSolaris zone to a local Mac OS  
X Server 10.5.machine. Both are running rsync 2.9.6.


The Solaris box has a filesystem mounted from NFS at /shared ... I am  
trying (in vein, so far) to backup it's internal root filesystem  
separately to it's NFS /shared filesystem.


I have noticed two problems which appear to be related. Essentially I  
think rsync on the solaris side is unable to tell that my /shared NFS  
partition is a separate filesystem from /.  Perhaps rsync is unable to  
correctly recognise properties of an NFS mounted filesystem from  
within a Solaris zone aka container?


Problem 1/  use of --one-file-system when copying / is ignored and  
the /shared filesystem is also copied


Problem 2/ when trying to just copy the /shared filesystem I also get  
the root filesystem!


Details...

Problem 1/

use of --one-file-system when copying / is ignored and the /shared  
filesystem is also copied ... My workaround to this is to also specify  
--exclude=/shared/ and then it doesn't get copied. But why is it  
unable to tell that /shared/ is a separate filesystem?


command line run from the Mac:

/usr/bin/rsync --stats -v \
  -e ${ssh} -i ${private_key} -b ${bind_address} -C  --bwlimit=$ 
{bwlimit} -a --delete-after --numeric-ids --one-file-system \

  --exclude=/proc/ \
  --exclude=/usr/ \
  --exclude=/lib/ \
  --exclude=/dev/ \
  --exclude=/sbin/ \
  --exclude=/bin/ \
  --exclude=/platform/ \
  --exclude=/system/ \
  --exclude=/etc/svc/volatile/ \
  ${host}:/. \
  ${dest}/

The above also copies the entire contents of the /shared filesystem.  
I've tried using -x instead of --one-file-system.



Problem 2/

when trying to just copy the /shared filesystem I also get the root  
filesystem! ... I don't have a workaround for this one. Although I'm  
specifying to only copy the contents of the /shared/ directory it  
instead copies the whole of the root filesystem AND the /shared/  
filesystem.


command line run from the Mac:

root 89707   0.0  0.076248944 s003  S+9:46AM
0:00.01 /usr/bin/rsync --stats -v -e /usr/bin/ssh -i /var/root/.ssh/ 
id_dsa -b whitegirl.local -C  --bwlimit=2000 -a --delete-after -- 
numeric-ids -x --exclude=/proc/ --exclude=/usr/ --exclude=/lib/ -- 
exclude=/dev/ --exclude=/sbin/ --exclude=/bin/ --exclude=/platform/ -- 
exclude=/system/ --exclude=/etc/svc/volatile/ accel2.carbonplanet.com:/ 
shared/. /Volumes/DATA/Backups/accel2.carbonplanet.com_shared/


child ssh process:

root 89708   0.0  0.177092   1500 s003  S+9:46AM
0:00.07 /usr/bin/ssh -i /var/root/.ssh/id_dsa -b whitegirl.local -C  
accel2.carbonplanet.com rsync --server --sender -vlogDtprx -- 
bwlimit=2000 --numeric-ids . /shared/.


I'm now going to try and build rsync 3.0.4 using pkg-src and mac ports  
on the solaris and mac boxes respectively, but I've been unable to  
find a bug recorded for 2.9.6 that would describe the above so I'm not  
hugely hopeful.


Anyone got any ideas?

Thanks very much
Jesse




  Jesse Reynolds - jesse.reyno...@carbonplanet.com
  Chief Technology Officer, Carbon Planet Limited, Australia. +61 2  
9319 9815

  http://www.carbonplanet.com/ You can be the change.



smime.p7s
Description: S/MIME cryptographic signature
-- 
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 compression still broken

2008-12-26 Thread Les Barstow

I've surfed through the archives and notice that no-one's resolved the
compression issue, nor has anyone reported it for a while.

I am sad to report that the issue still appears to exist in 3.0.4. 
Conditions seem similar to other instances reported where the file is 1GB. 
And, like those other reports, I have unfortunately overwritten the
destination file when I turned off the compression flag and got a successful
copy.

Sorry I can't provide more,
--
Les Barstow, System Administrator
Profitool, Inc.
-- 
View this message in context: 
http://www.nabble.com/Rsync-compression-still-broken-tp21179399p21179399.html
Sent from the Samba - rsync mailing list archive at Nabble.com.

-- 
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: Rsync compression still broken

2008-12-26 Thread Matt McCutchen
On Fri, 2008-12-26 at 14:07 -0800, Les Barstow wrote:
 I've surfed through the archives and notice that no-one's resolved the
 compression issue, nor has anyone reported it for a while.
 
 I am sad to report that the issue still appears to exist in 3.0.4. 
 Conditions seem similar to other instances reported where the file is 1GB. 
 And, like those other reports, I have unfortunately overwritten the
 destination file when I turned off the compression flag and got a successful
 copy.

Yes, we know, but we can't find out for sure what is causing the problem
until someone provides a reproducible test case.  If you like, you can
enter a bug at https://bugzilla.samba.org/ (there isn't one yet) to keep
links to all the relevant threads in one place.

Wayne speculated a while ago that the cause may be false matches in the
delta-transfer algorithm, and that seemed reasonable to me:

http://lists.samba.org/archive/rsync/2008-October/021889.html

but I don't think this angle has been pursued.

-- 
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


Re: Windows 2003 Cygwin Netapp remote filesystem

2008-12-26 Thread Matt McCutchen
On Fri, 2008-12-26 at 14:13 -0700, Michael Chletsos wrote:
 Ok so I have figured out the problem with my rsync daemon is the fact
 that rsync interprets // as / and therefore is not seeing this as a
 unc path, but rather a absolute path.

This should be fixed in rsync 3.0.5pre2 as well as the latest
development rsync.  See:

http://lists.samba.org/archive/rsync/2008-November/022127.html
http://gitweb.samba.org/?p=rsync.git;a=commit;h=5436b6455728608a5b5a62da01eb74dc440f1aac

-- 
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