Rsync just hangs..

[Siyfion]

So I have three shares on a ReadyNAS 3200 that I'd like to sync with a ReadyNAS Pro 4 which is used as an in-house backup, before the data is eventually backed up onto external HDDs and removed off-site. The share's contain a fairly sizeable amount of data 100s of GB.

No matter what I do, I cannot get the 3200 to backup the three shares to the Pro 4. Ideally I'd like to get the first data backed up using a standard NFS backup then switch to a Rsync incremental backup that will run every few hours each day.

When attempting to backup using NFS shares from the Pro "pulling" data from the 3200, it never gets started, just hangs. If I "push" the data from the 3200 to the Pro, it starts and very slowly copies some files over, then the 3200 Frontview stops responding and the backup simply halts.

If I try to do the first backup using Rsync, no matter which way around I try it, they always both get stuck at "receiving incremental file list" and while neither locks-up or fails to respond, nothing actually happens (I've left it for 7 days+ once and still nothing).

[mdgm-ntgr]

What version of RAIDiator is on the units?

[Siyfion]

Oh I suppose I should give some more information about the devices / software:

Model: ReadyNAS 3200 v1 [X-RAID2]
Firmware: RAIDiator 4.2.22
Memory: 4096 MB [DDR2]
IPv4 address: 1+2: 192.168.0.157

Model: ReadyNAS Pro 4 [X-RAID2]
Firmware: RAIDiator 4.2.24
Memory: 1024 MB [DDR2]
IPv4 address: 1+2: 192.168.0.158

Both devices have their network interfaces in teaming mode (IEE 802.3ad LACP - Layer 2).

[mdgm-ntgr]

Have you tried contacting support?

[Siyfion]

Not as yet, I thought I'd try here first...

[mdgm-ntgr]

Is either NAS under heavy load? Have you checked to see if the 4GB OS partition is very full one other unit?

[Siyfion]

The ReadyNAS 3200 is probably under a reasonable workload as it's the main VMware NFS host..

Is there an easy way to see what load it's actually under?

[mdgm-ntgr]

Well if you are comfortable with the support implications of enabling SSH you could run top

[Siyfion]

Two questions; how likely are support to refuse to help if I've enabled SSH access? Do I need to reboot the NAS to enable SSH? (if so, no can do until out of business hours)

[mdgm-ntgr]

I would suggest you download your logs (Status > Logs > Download all logs), open an online case and attach your logs to your case.

[Siyfion]

By CPU:


By MEM:

[mdgm-ntgr]

That looks like a pretty light load.

What's the output of

# df -h

[Siyfion]

Yeah, I mean while it's the main NFS datastore for the VMs, there a) aren't that many VMs and b) even less that actually do very much work... (There's 1 with SQL server installed and an accountancy package server, probably make up 99% of the usage)

[mdgm-ntgr]

I think you should contact support for assistance.

[Siyfion]

I've just sent a request and linked this thread...

Is it normal for that amount of memory to be used? I mean, there's barely any available and none of the processes seem to be using any...?

[mdgm-ntgr]

It's normal.

If you look at the logs or do

# cat /proc/meminfo

You will see that a lot of RAM is used for caching to improve performance. The memory will be freed up if needed for other tasks.

[AlexPe]

Some questions,

1. What are you rsyncing source and destination?
2. Are you able to rsync to the 3200 as the destination vice versa?
3. Are you initiating this job from the GUI or command line?

[8ohmh]

Holger Ohmacht aka h8ohmh / 8ohmh:

The problem lies in the filesystem buffer / usage of the interworking of harddisk/hw so far as I could investigate.

Temporal solution for local drives (eg. USB3<->HD) : A script which is polling the changing disk space. If no changing free disk space then rsync is stalled and have to be restarted

    cmd="rsync -aW --progress --stats --preallocate --super <here your source dir> <here your dest dir>" 
    eval "$cmd" &  
    rm ./ndf.txt rm ./odf.txt 
    while [[ 0 == 0 ]]; do
            df > ./ndf.txt
            cmp ./odf.txt ./ndf.txt
            res="$?"
            echo "$res"
            if [[ $res == 0 ]]; then
                    echo "#################################################"
                    ls -al "./ndf.txt"
                    ls -al "./odf.txt"
                    killall rsync
                    eval "$cmd" &
            else
                    cp ./ndf.txt ./odf.txt
            fi
            sleep 60 
    done

`
Change `<source dir>` etc to your paths!

In my case it is always stalling after some few 100's files  by usage of rsync's --preallocate option  files (normally because of better disk performance and rescueing continuous blocks), so as long as the disk and filesystem drivers not reworked there just this solution