does the ReadyNAS have rsync or are you just mounting up the NFS share
locally? If you are trying to use rsync then I suspect that the ReadyNAS
doesn't have enough RAM. Also, how much RAM does your system have? and are
you using rsync? rsync eats up RAM like candy when you have a high file
count. would you do a `find /path/to/data|wc -l` and post that number? if
you take than number and multiply by 100, then divide by 1024 and you will
see how many KBytes of RAM required for a single sided rsync. if you are
using rsyncd remotely and rsync locally, then you need this amount of ram on
each side.
On Mon, May 5, 2008 at 7:12 AM, Leandro Tracchia <[EMAIL PROTECTED]>
wrote:
> well it turns out the terastation does not even support NFS, however it
> does support Windows shares. I do have another NAS, a ReadyNAS which does
> support NFS so i decided to try this one out and started a full backup job
> to let it run over the weekend. Uncompressed, the data needed to backup is
> about 475GB. This is actually 3 different shares (A-F\:
> 250GB,G-N\:63GB,O-Z\: 160GB). Well hoping to see a successful backup monday
> morning, i came to work seeing that the backup had failed! it ran for about
> 5 hours until i got some "PIPE" error and then after that i got a "Child
> exited prematurely" error.
>
> 2008-05-02 11:56:49 full backup started for directory A-F
> 2008-05-02 17:07:38 Aborting backup up after signal PIPE
> 2008-05-02 17:07:40 Got fatal error during xfer (aborted by signal=PIPE)
> 2008-05-02 17:07:45 Saved partial dump 0
> 2008-05-02 20:00:06 full backup started for directory A-F
> 2008-05-02 22:54:40 Got fatal error during xfer (Child exited prematurely)
> 2008-05-02 22:54:45 Backup aborted (Child exited prematurely)
> 2008-05-02 22:54:45 Saved partial dump 0
> 2008-05-03 20:00:02 full backup started for directory A-F
> 2008-05-04 17:14:22 full backup started for directory G-N
> 2008-05-04 22:46:52 full backup started for directory O-Z
>
> fortunately it seems to have saved the partial backup and automatically
> restarted the job. though, i'm not sure what these errors mean or if they
> have anything to do with the NFS mount or if these errors are even
> documented anywhere or if they will happen again.
>
> any suggestions???
>
> (thank you for all the help so far, btw!!)
>
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
