I am trying to use a large (10TB) reiserfs filesystem as an rsync target. The filesystem is on top of lvm2 (pretty sure this doesn't matter, but just in case.) I get the following error when trying to sync a modest set of files to that 10TB target (just syncing /etc for now): rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) When I encountered the error, I suspected a problem with the filesystem size, so I started testing with 2TB, 4TB, 8TB filesystems. (I started with 2TB and grew the LV and resized the reiserfs each time.) Just under 8TB (7.45TB) everything worked fine. After going just over 8TB (8.45TB) I got the error again. Just for kicks, I tried syncing a single new file and that worked. I then tried syncing a single new directory, and that worked as well. You can see below these steps, as well as the directory the original /etc sync failed on. I have listed the contents of that directory and the following directory in case it has pertinence here. Is anyone else using > 8TB targets for rsync with success? I have kept this to a local rsync to eliminate variables with ssh/rsyncd/network. thanks in advance, matt Matt Miller IT Infrastructure Duke - Fuqua School of Business -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 1393 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20040810/5d337cad/attachment.bin
Actually... a cp -r has the same issues... anyone seen this? BTW, I'm on SuSE 9.1 (personal) with the 2.6 kernel, lvm2, reiserfs, 2G RAM, 2G swap matt On Aug 10, 2004, at 4:41 PM, Matt Miller wrote:> I am trying to use a large (10TB) reiserfs filesystem as an rsync > target. The filesystem is on top of lvm2 (pretty sure this doesn't > matter, but just in case.) I get the following error when trying to > sync a modest set of files to that 10TB target (just syncing /etc for > now): > > rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": > Broken pipe > rsync error: error in rsync protocol data stream (code 12) at io.c(836) > > When I encountered the error, I suspected a problem with the > filesystem size, so I started testing with 2TB, 4TB, 8TB filesystems. > (I started with 2TB and grew the LV and resized the reiserfs each > time.) Just under 8TB (7.45TB) everything worked fine. After going > just over 8TB (8.45TB) I got the error again. > > Just for kicks, I tried syncing a single new file and that worked. I > then tried syncing a single new directory, and that worked as well. > You can see below these steps, as well as the directory the original > /etc sync failed on. I have listed the contents of that directory and > the following directory in case it has pertinence here. > > Is anyone else using > 8TB targets for rsync with success? I have > kept this to a local rsync to eliminate variables with > ssh/rsyncd/network. > > thanks in advance, > > matt > > > > Matt Miller > IT Infrastructure > Duke - Fuqua School of Business-- > To unsubscribe or change options: > http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: > http://www.catb.org/~esr/faqs/smart-questions.htmlMatt Miller IT Infrastructure Duke - Fuqua School of Business -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 1912 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20040811/42957a5d/attachment.bin
On Tue, 10 Aug 2004, Matt Miller m.miller-at-duke.edu |Rsync List| wrote:> I am trying to use a large (10TB) reiserfs filesystem as an rsync > target. The filesystem is on top of lvm2 (pretty sure this doesn't > matter, but just in case.) I get the following error when trying to > sync a modest set of files to that 10TB target (just syncing /etc for > now): > > rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": > Broken pipe > rsync error: error in rsync protocol data stream (code 12) at io.c(836)This is unfortunately a fairly generic error message that means the remote/child process died suddenly without passing back any information about why. Here's a message from Wayne on why the error message is so generic: http://lists.samba.org/archive/rsync/2004-July/010204.html I'd suggest following the same debugging steps I used to track down a 2GB bug on HP-UX: http://lists.samba.org/archive/rsync/2004-July/010197.html The best results were from running rsync under "tusc" (in your Linux case it would be "strace") and sifting through the voluminous output to find the write() that failed and why. -- Steve
On Tue, Aug 10, 2004 at 04:41:56PM -0400, Matt Miller wrote:> rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe > rsync error: error in rsync protocol data stream (code 12) at io.c(836)As I just replied to another message on the list, this error just means that the other side went away for some reason. What you need to figure out is why. The version of rsync in CVS (and in the "nightly" tar files) tries to grab a dying error from the other side, if possible. This is coverend on the "known issues" page: http://rsync.samba.org/issues.html So, I'd recommend trying the CVS version of rsync to see if that gives you the actual error of what failed. Alternately (or additionally), follow the directions on the issues page to get a core dump and/or a system-call trace from the remote side to get extra information on what has gone wrong. ..wayne..