This looks like it should work, but does not? HOME1 and BOX48 are NFS servers mounted on box10 but the data does not get transferred from HOME1 [box8] to BOX48.
[bobg@box10 ~]$ rsync -avz /mnt/HOME1/notecase/notecase/STUFF.ncd /mnt/BOX48/notecase/STUFF.ncd It just reports:
sending incremental file list STUFF.ncd
sent 539506 bytes received 31 bytes 359691.33 bytes/sec total size is 1196229 speedup is 2.22
However after saving the file to a new directory on box10 I can then rsync from that into the second server box48 despite the error message about some files/attrs.
[bobg@box10 ~]$ rsync -avz /mnt/HOME1/notecase/notecase/STUFF.ncd /home/bobg/NOTES/
[bobg@box10 ~]$ rsync -avz /home/bobg/NOTES/STUFF.ncd /mnt/BOX48/notecase/STUFF.ncd sending incremental file list STUFF.ncd rsync: chgrp "/mnt/BOX48/notecase/.STUFF.ncd.kBIUjd" failed: Operation not permitted (1)
sent 539834 bytes received 31 bytes 359910.00 bytes/sec total size is 1196982 speedup is 2.22 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1052) [sender=3.0.9]
Can anyone tell me what I am doing wrong?
Bob .
Am 13.03.2013 15:23, schrieb Bob Goodwin - Zuni:
[bobg@box10 ~]$ rsync -avz /home/bobg/NOTES/STUFF.ncd /mnt/BOX48/notecase/STUFF.ncd sending incremental file list STUFF.ncd rsync: chgrp "/mnt/BOX48/notecase/.STUFF.ncd.kBIUjd" failed: Operation not permitted (1)
sent 539834 bytes received 31 bytes 359910.00 bytes/sec total size is 1196982 speedup is 2.22 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1052) [sender=3.0.9]
you can not use -avz because it contains --owner --group which is NOT allowed for a ordinary user and you are one in case of a NFS mount
On 13/03/13 10:26, Reindl Harald wrote:
Am 13.03.2013 15:23, schrieb Bob Goodwin - Zuni:
[bobg@box10 ~]$ rsync -avz /home/bobg/NOTES/STUFF.ncd /mnt/BOX48/notecase/STUFF.ncd sending incremental file list STUFF.ncd rsync: chgrp "/mnt/BOX48/notecase/.STUFF.ncd.kBIUjd" failed: Operation not permitted (1)
sent 539834 bytes received 31 bytes 359910.00 bytes/sec total size is 1196982 speedup is 2.22 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1052) [sender=3.0.9]
you can not use -avz because it contains --owner --group which is NOT allowed for a ordinary user and you are one in case of a NFS mount
Then what should I do, drop the "a", just -vz?
On 13/03/13 10:46, Tom Horsley wrote:
On Wed, 13 Mar 2013 10:34:20 -0400 Bob Goodwin - Zuni, Virginia, USA wrote:
Then what should I do, drop the "a", just -vz?
Well, the best thing to do is not get NFS involved at all, do the rsync directly between the machines hosting the different directories.
Yes, that works I know. It just seemed I should be able to do that one file which reduces the chance of corrupting the whole disk. I should do them both as you say since there is other stuff I need to keep sync'd also.
Tnx,
Bob
On 13/03/13 10:46, Tom Horsley wrote:
Well, the best thing to do is not get NFS involved at all, do the rsync directly between the machines hosting the different directories.
Those servers don't normally have keyboards or displays. I can always deal with that but don't want to do it often. What I really need is a script that I could start via ssh, probably on box8 the source, that would rsync box48 to it.
On 03/13/2013 09:45 AM, Bob Goodwin - Zuni, Virginia, USA issued this missive:
On 13/03/13 10:46, Tom Horsley wrote:
Well, the best thing to do is not get NFS involved at all, do the rsync directly between the machines hosting the different directories.
I concur. NFS puts certain restrictions on things that you may not want and NFS is not the fastest protocol to use--especially if you're writing to the NFS server.
Those servers don't normally have keyboards or displays. I can always deal with that but don't want to do it often. What I really need is a script that I could start via ssh, probably on box8 the source, that would rsync box48 to it.
Try to set up rsync daemons on the various boxes (man rsyncd.conf). Set up "hosts allow" and "hosts deny" options for the various modules (directories) you want involved to restrict rsync access. You can also set up user/password stuff and either have rsync run in daemon mode or from xinetd. We use it a TON.
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Admitting you have a problem is the first step toward getting - - medicated for it. -- Jim Evarts (http://www.TopFive.com) - ----------------------------------------------------------------------
On 13/03/13 12:54, Rick Stevens wrote:
On 03/13/2013 09:45 AM, Bob Goodwin - Zuni, Virginia, USA issued this missive:
On 13/03/13 10:46, Tom Horsley wrote:
Well, the best thing to do is not get NFS involved at all, do the rsync directly between the machines hosting the different directories.
I concur. NFS puts certain restrictions on things that you may not want and NFS is not the fastest protocol to use--especially if you're writing to the NFS server.
Those servers don't normally have keyboards or displays. I can always deal with that but don't want to do it often. What I really need is a script that I could start via ssh, probably on box8 the source, that would rsync box48 to it.
Try to set up rsync daemons on the various boxes (man rsyncd.conf). Set up "hosts allow" and "hosts deny" options for the various modules (directories) you want involved to restrict rsync access. You can also set up user/password stuff and either have rsync run in daemon mode or from xinetd. We use it a TON.
Ok, I'll see if I can implement something like that.
Thank you,
Bob
-
Bob Goodwin -
Reindl Harald -
Rick Stevens -
Tom Horsley