We have seen this intermittently, but usually on getimage. It appears to be related either a) the size of the image, or B) the number of file systems, or c) the --exclude option. At first we were running getimage with --exclude /scratch/*, and getimage would fail with various rsync errors. If we unmount the fs we don't want, /scratch in our case, and run getimage w/o the --exclude, it completes normally. This just happened yesterday and we haven't had time to troubleshoot it.
At first we thought it was our image server since its old and had
some weird hd issue, but a new machine had similar problems until we tried the above.


Running 3.2.2 on debian

Sandy Spence wrote:
Hi All,



I have made a number of attempts to copy an image onto a new node, each time it fails with an rsync error message in the form



unexpected tag 78

or

unexpected tag 113, etc etc



I have tried the rsync from different machines and each time I get the same error message



I am running RH9 with dual AMDs and Systemimager 3.2.



The getimage works like a dream, or at least appears to, very fast.



Can anyone point me in the right direction?



Cheers,



Sandy Spence



Computer Officer, RA Certification Manager

Department of Computer Science - UWA

Llandinam Building

Penglais Campus

Aberystwyth

Ceredigion

Wales - UK

SY23 3DB

Tel: (01970)-622433

Fax: (01970)-628536





--
George Kelbley                  System Support Group    
Computer Science Department     University of New Mexico
505-277-6502                    Fax: 505-277-6927


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to