similar to: more info for rsyncs not exiting problem

I'm having a problem where my rsync processes don't exit. They finish their task.. but they don't exit. I'll see at the end, if i'm running -vv, something like: total: matches=727 tag_hits=771 false_alarms=0 data=2034655738 but the process continues to run, but not do anything apparent. If I strace the process, I see a ton of: select(0, NULL, NULL, NULL, {0, 1000}) = 0

Hello, I was wondering if its possible to extract the checksum that rsycn creates to verify the transfer of a file was successful? Id like to store it so I can verify the files at a later time. I was thinking I could just run an md5sum prior to rsync, but then I figured if rsycn is already doing it maybe I can just copy that checksum. I have sever tb's of smaller files I need to transfer so

Timo Sirainen <tss at iki.fi> wrote: > Two potential problems I see with this: > 1. If users can do any changes on the secondary server (flag changes, > saving new mails, etc), you're going to have problems syncing the > changes back (without losing any changes or causing other problems). > > 2. If users can access the secondary server via IMAP clients, the > clients

hi guys, we are using rsycn without problem but today after some problems in one of the servers, the dc tech did find the rsync is effecting in the switch where they have the server connected broadcasting all the ports in the switch at the dc????? This is what the dc tech said: "It appears that your server is broadcasting to every port on the switch that you are connected to" Any

I'm considering using rsync in our data center but I'm worried about whether it will scale to the numbers and sizes we deal with. We would be moving up to a terabyte in a typical sync, consisting of about a million files. Our data mover machines are RedHat Linux Advanced Server 2.1 and all the sources and destinations are NFS mounts. The data is stored on big NFS file servers. The

If I use -v or -vv, the rsyncs will hang forever (or at least a few days, I haven't let them run any longer than that so I'm nto sure if they'd eventually exit on their own or not). The information on rsync and OS version was sent in my previous email. For now i'm just going to run without -v, as I need to get this going and don't have time to get intimately involved with

Hi, I'm having a MAJOR issue with an rsync backup script that is actually OVERWRITING the files that it should be backing up! The thing is, the same script (with different source/destination variables) runs FLAWLESSLY on another file server! Background: 2 OS X client computers running 10.4.11 (1 intel, 1 PPC). both are running rsync v2.6.3. rsync is backing up from one firewire HD(afp

Hi, I'm getting the following errors from smbd every night... The error log will grow to consume all the file space on the system. Sep 18 06:00:00 seawolf smbd[2257]: [2002/09/18 06:00:00, 0] lib/util_str.c:string_sub(1188) Sep 18 06:00:00 seawolf smbd[2252]: [2002/09/18 06:00:00, 0] lib/util_str.c:string_sub(1188) Sep 18 06:00:00 seawolf smbd[2251]: [2002/09/18 06:00:00, 0]

I have a local directory that I am trying to sync with a remote directory. That's fine, but there's a lot of data that is out of sync so I decided to make a local copy of the difference to then bring to the remote location. So I ran a dry-run between the two to generate a list of files in listOfFiles.txt Then I ran rsync from local to localBackup. rsync -av

Bugs item #7503, was opened at 2006-12-30 19:28 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=7503&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 3 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Segfaults on exception, related to sizer Initial Comment: In

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hi! I've upgraded my seawolf to ext3fs with the packages from Roswell (kernel, filesystem, mount, ....), but when doing 'tune2fs -j', it mentions 'Ext3fs version 0.0.5b'...? Isn't version 0.0.7a the latest?? Why isn't that version included in the Roswell kernel, but an older version is? And how can i upgrade my version of ext3fs? Thanks! Bart Verwilst

On 04/01/2015 04:43 PM, Alain P?an wrote: > Le 01/04/2015 22:15, Lamar Owen a ?crit : >> It is impossible to satisfy everyone. > > So, you refuse to hear your users, who have stated good arguments, for > something that is not very difficult to change, the name of the iso, > which is not coherent with the 7.0 name and confusing ? It is only confusing if you let it confuse

I have a problem with rsync causing a filesystem to think that it is 100% used when actually it isn't. A quick reboot will cause the filesystem to go to about 70%-75% used. Below is the script that I am executing. I am using Red Hat Linux release 7.1 (Seawolf) Kernel 2.4.9-34smp on a 2-processor i686. Does anyone have any idea on what causes this and how to fix this? #!/bin/bash export

----- Original Message ----- From: Simon Hobson <linux at thehobsons.co.uk> To: "rsync at lists.samba.org" <rsync at lists.samba.org> Cc: Sent: Friday, June 26, 2015 8:07 AM Subject: Re: Sync files-from with delete john espiro <john_espiro at yahoo.com> wrote: > I have a local directory that I am trying to sync with a remote directory. That's fine, but

I was wondering if there is an answer to this challenge or if I just have to live with it? I'm a bit of a Newbie here. I'm in the process of setting up Samba -2.2.2 on a Redhat v7.1 (Seawolf) server. I've discovered that joining the NT Domain is a simple matter of smbpasswd -j DOMAIN_NAME smbpasswd picks up the PDC name from smb.conf and moves right along. There is no need to

https://bugzilla.samba.org/show_bug.cgi?id=2645 Summary: --one-file-system semantics changed with 2.6.4 (bug?) Product: rsync Version: 2.6.4 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Does rsync has directory name length limit? I was trying to rsync a directory that has the name length of 34 characters and getting permission denied error. $ rsync -avz --delete --force -e ssh /usr/local/apache/htdocs 192.168.0.2:/usr/local/apache building file list ... readlink htdocs/CorporateLegalTimesEDITORIAL_files/cBug_blueXs.gif: Permission denied readlink

I have noticed that if you run two rsyncs at once, they get confused and copy the files from one the wrong rsync thread. Apparently this is because of the ?Build List? that is made in ram. Two build lists stepping on each other. Does anyone know how to change the source so that the each build list in ram is kept separate?