Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <200206081319.g58DJGQp011216@dev1.bogus> To: cygwin AT cygwin DOT com cc: sgk AT kleinmann DOT com Subject: Re: tar, scp hang after upgrades In-reply-to: Your message of "Fri, 07 Jun 2002 13:53:10 EDT." <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020607134851 DOT 029b8900 AT pop DOT ma DOT ultranet DOT com> Date: Sat, 08 Jun 2002 09:19:16 -0400 From: Susan Kleinmann More tests (which I think show that the problem is really associated with the recent Windows ME upgrade): I tried the same steps on a machine running Windows 98SE. 1. Upgrade both Windows 98 and cygwin to latest versions. 2. Use scp to fetch a tar file from another machine. 3. Try to untar. Worked fine. (Note: This machine has an oldish (4.0) version of NAV, which doesn't work in auto-mode; i.e., it scans for viruses only when/if specifically invoked to do so.) Then I retried steps 2-3 above on the machine running WindowsME, which, as I said earlier, was updated a few days ago. The results were: 1. With NAV enabled, scp succeeded, but tar continued to hang as before. (scp had hung the last 2 dozen or so times I tried it, but see below: the behaviour is not always exactly repeatable.) 2. With NAV disabled, scp succeeded, and tar completed, but reported several "Wrote only 0 out of 10240 bytes" errors, and did not extract most of the files in the tar file (even though it was easily able to 'see' them all using 'tar -tf filename'). So, with NAV turned off, I ran the command: strace tar -xf foo.tar > tar.errors 2>&1 This produced the following errors just prior to the "Wrote only..." message: 2021282 2597075 [main] tar 1735255 seterrno_from_win_error: /cygnus/netrel/src/cygwin-1.3.10-1/winsup/cygwin/fhandler.cc:279 errno 29 1105 2598180 [main] tar 1735255 geterrno_from_win_error: unknown windows error 29, setting errno to 13 435 2598615 [main] tar 1735255 fhandler_base::write: -1 = write (0x4591E68, 698) 250 2598865 [main] tar 1735255 _write: -1 = write (4, 0x4591E68, 698) 432 2599297 [main] tar 1735255 _write: write (2, 0x255F39C, 5) 338 2599635 [main] tar 1735255 fhandler_base::write: binary write tar: 265 2599900 [main] tar 1735255 fhandler_base::write: 5 = write (0x255F39C, 5) 240 2600140 [main] tar 1735255 _write: 5 = write (2, 0x255F39C, 5) 272 2600412 [main] tar 1735255 _write: write (2, 0x255F3CC, 40) 255 2600667 [main] tar 1735255 fhandler_base::write: binary write week2/aux.c: Wrote only 0 of 10240 bytes 265 2600932 [main] tar 1735255 fhandler_base::write: 40 = write (0x255F3CC, 40) Inconsistencies: I notice that the output to screen from tar -xf foo.tar sometimes seems to extract a few files before it starts to display "Wrote only 0 bytes..." messages. (I am only speaking here of the situation with NAV turned off, because there is no output at all when NAV is turned on.) Conclusion: the geterrno_from_win_error: unknown windows error 29, is a red flag, suggesting to me that some aspect of the last WindowsME upgrade started a problem. I appreciate the quick response I got yesterday, and now request some new suggestions/tests that might lead to a resolution of this problem. Thanks, Susan > At 01:35 PM 6/7/2002, Susan Kleinmann wrote: > >In the last few days, I updated cygwin, Windows ME, and Norton anit-virus > >(I think, but am not sure, that was the order.) I do this every once a > >month or so. > > > >Since the latest round of upgrades, both tar and scp seem to hang the > >machine, so that all I can do to recover is to remove the battery > >and powercord to reboot. > > > >Is there some important patch/configuration that I missed? > > > Not obviously, no. I have the latest Cygwin DLL and NAV updated itself > just today even. I have no trouble using "tar" on a file I had. Of > course, I'm on W2K. The results of strace might help locate the problem > though, assuming it's Cygwin-based. Disabling NAV while you run tar or > scp would help pinpoint if the problem is NAV. > > > > Larry Hall lhall AT rfk DOT com > RFK Partners, Inc. http://www.rfk.com > 838 Washington Street (508) 893-9779 - RFK Office > Holliston, MA 01746 (508) 893-9889 - FAX > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/