<div class="gmail_quote">On Thu, Apr 22, 2010 at 6:45 PM, mm_half3 <span dir="ltr"><<a href="mailto:mm_half3@yahoo.com">mm_half3@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I noticed an unexpected problem in the sync log files, one of the user data directories had bumped up against it's quota, and failed to write the data. That is expected, what was unexpected was the entire rsync process died with this error, and the remaining user file systems in the rsync job, about 100 or so did not get written.</blockquote>
<div><br></div><div>Yeah, rsync explicitly dies if it gets an I/O error that it interprets as a lack of space. Typically this means that the entire destination disk has filled up, and trying more copying is futile. In some cases that assumption is not warranted, but it is the most common.</div>
<div><br></div><div>There are potential ways to improve this, but most of them require making rsync smarter about being able to query quotas and destination disk amounts at different spots in the hierarchy, which is not a simple change to make.</div>
<div><br></div><div>The already-suggested idea to split the job into separate per-quota copies is probably your best bet for now.</div><div><br></div></div>..wayne..<br>