similar to: rsync to a destination > 8TB problem...

Greetings. I am trying to create a 10TB (approx) ext3 filesystem. I am able to successfully create the partition using parted, but when I try to use mkfs.ext3, I get an error stating there is an 8TB limit for ext3 filesystems. I looked at the specs for 5 on the "upstream" vendor's website, and they indicate that there is a 16TB limit on ext3. Has anyone been able to create

I have seen this error in many postings, but the solutions seem not to apply in this case. This error happens during a small file transfer (gif image) and after 75% of a 165G rsync job (the building file list portion is complete.) Most solutions I saw were related to not having enough RAM or running out of disk space. Check out the machine specs below the error. rsync: writefd_unbuffered

Rsync 2.5.5; transfer via ssh; sparc-sun-solaris2.5 (Ultra 1); gcc 2.8.1. Every time rsync on this box causes boundary violation. I attached two strange examples. I have a few rsync's corefiles (100MB and above) and I can examine them. I will be grateful for any help. -Mirek <-------------------------------------------------------------------------> received 966761 names done

Hi, i installed rsync 3.0 on a Sun Solaris 10 Sparc Server and tried to Backup the Server via BackupPC the complete rsync command from the backup server is this: /usr/bin/ssh -q -x -l root IP /usr/bin/rsync --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --log-file=/var/log/rsync.log --ignore-times . / in the log on

Hi, I receive this error when rsyncing. I suspect this is because of network problems. But the 'Invalid argument' and 'phase unknown' makes it very unobvious. ... packages/scribus/scribus-1.2.3-0.rf.src.rpm Read from remote host rsync.sw.be: Invalid argument rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown" [sender]: Broken pipe (32) rsync:

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >

Hi All. On Mac OS10.4, using rsync 3.0, it stops during a transfer. I mount an SMB share, and then use the line: sudo rsync -avhi --delete --stats --timeout=360 --progress --log-file=/Volumes/backup/20080429/rsynclog.txt --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 There's a few terabytes of data, and it never finishes a complete run. It can stop at anywhere during

https://bugzilla.samba.org/show_bug.cgi?id=6175 Summary: write last transfer status when timeout or other error happens Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Periodicaly rsync terminates with folowing errors: unexpected tag -55 [receiver] file has vanished: "<filename here>" server log says: file has vanished: "<filename here>" (in userdata) writefd_unbuffered failed to write 4 bytes [sender]: Connection reset by peer (104) I'm didn't wondered with vanished file, but what is "unexpected tag" and

https://bugzilla.samba.org/show_bug.cgi?id=7195 Summary: timeout reached while sending checksums for very large files Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org

I am doing a large and long transfer and twice now i have gotten this error killing the transfer, anyone know what/how i can fix this? root@denali [/etc/rsync]# Received disconnect from 66.160.191.130: 2: Corrupted MAC on input. rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync: connection unexpectedly closed (1055144 bytes received so

Hello, 2010/11/15 17:40:32 [3200] rsync: writefd_unbuffered failed to write 8 bytes [generator]: Broken pipe (32) 2010/11/15 17:40:32 [3200] rsync error: error in rsync protocol data stream (code 12) at io.c(1550) [generator=3.0.4] What's mean this log ?? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm getting the following error occasional and can't find out why; 05/14/2011 09:28:51 rsyncing /dbtmp to /dbtmp.new (1st pass) .... rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/dbtmp.new/file.dmp": File too large (27) rsync error: error in file IO (code 11) at receiver.c(258) [receiver=2.6.9] rsync: connection

Yes this is another connection reset issue but all I am asking is some pointers on how I can possibly determine what and why this is happening. Its easy to say its a network issue but the bosses and clients want to know how to fix this said "network issue." I have read the rsync issues list. Some of what is suggested we might try HOWEVER we cannot duplicate the errors that occur and

Hi, I'm having a problem rsyncing one file (since I signed it). It seems that the content of a file is able to cause problems in the protocol. building file list ... 28820 files to consider apt/packages/avifile/ apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code

Hello, i use rsync from Windows to rsync on Linux via ssh and get IO Errors and connection unexpectedly closed errors on almost every sync run. Can anybody give me some hints on how to track down the problem? thx, Chris 2008/10/11 09:41:04 [13744] rsync to backup// from UNKNOWN (w.x.y.z) 2008/10/11 09:41:04 [13744] receiving file list 2008/10/11 09:42:48 [13744] IO error encountered -- skipping

I am using Rsync 2.6.3 , and have tried rsync 2.6.2 also. I am attempting to push about 990G from one machine to another. Whenever I do this, it processes about 1/3 the way through and I receive the following error during the transfer, and it stops. Could this be a problem with it running as a cron job? The command I am using is /usr/local/bin/rsync -acv --stats /data/ server::data Any

Hello! A good day to you all. i've installed rsync-2.5.6 on a Red Hat 9.0 box(server) and am using rsync 2.5.6 on a Red Hat 6.2 box(client). In the middle of the rsync transfer, i get the error on the client saying that the server unexpectedly close the connection. Upon checking the logs on the rsync server, i found this entry: Oct 10 14:39:38 linux01 rsyncd[9266]: rsync:

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From admin@exovian.com 2005-04-21 08:46 ------- root@xxxx [~]# rsync -avz -e ssh /home/ xxxx@xxxxx:xxxx building file list ... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) This method