CentOS 7 Rsync Problem

Home » CentOS » CentOS 7 Rsync Problem
CentOS 1 Comment

Hello list.

I have a problem with rsync on a FUJITSU PRIMERGY TX150 S7 mailserver with Linux version 3.10.0-862.11.6.el7.x86_64. The server have a hardware raid 5 megaraid_sas and xfs partitions.

I have an external network disk (mounted as cifs) where we backup emails from old CentOS 6 mailserver and files from also CentOS 6 file server.

On the new mail server with CentOS 7 (full updated) the rsync starts but stop transferring files after some minutes and disappears from Top but service is alive on ps aux.

The email files (cyrus imap files) are mostly small files.

Unfortunately there is no error so I cant understand where is the problem. We try an external usb (ext3) and transfer 40Gb emails without problem.

We give the command:

rsync -vaR –delete –log-file=/var/log/rsync /var/lib/imap
/var/spool/imap/ /mnt/backup/mailserver/

Any ideas?

Thank you in advance.

CentOS 7, Rsync Problem

Home » CentOS » CentOS 7, Rsync Problem
CentOS 3 Comments

Oddity: rsync *should* be recursing, and dealing with very large number of files. It works, going from box a to box b. But when I try to back b up to c, it fails, 100%, complaining of “out of hashtable space [sender]”. I’ve tried adding -r, and changing –delete to –delete-delay, and no joy.

All boxes are current, or fairly current, CentOS 7.

Anyone got any thoughts on the matter?

mark

3 thoughts on - CentOS 7, Rsync Problem

  • The only thing I know of that’s likely to cause rsync to run out of memory is when there are a huge number of hard links and you are using the “-H”
    option to preserve them. (If you think you don’t have many, look under
    /var/lib/yum/yumdb and /usr/share/zoneinfo.)

    And FYI, rsync doesn’t do a very good job of preserving hard links when going to a destination that already has some of the files. It doesn’t break any existing hard links at the destination, so you can end up with a hard link topology that is somewhat different from the source. I have to run some very messy audits to make sure all copies of my backups have the same arrangement of hard-linked files.

  • If you’re using -H, rsync has to keep a table of all of the files and inode/device number combinations. It’ll actually consume *more* memory if you have a smaller number of hard-linked files.

  • It only needs to keep track of that for files that have a link count greater than 1 in their inodes.