Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Hannu E K Nevalainen (garbage mail)" To: Subject: RE: Peculiarities with tar Date: Tue, 15 Apr 2003 23:02:32 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: Importance: Normal > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf > Of Andrew Markebo > / "Hannu E K Nevalainen (garbage mail)" > wrote: --8<-- > | //FUJITSU2/ is a 200MHz P2 and has McAfee 5.21 running on it. > | McAfee checks the files as they're read - does that affect > tar's behaviour? > > I recognize this, saw similar problem, disappeared when disabling the > McAfee antivirus, give that a try.. > > How to get it fixed, turn off mcafee while backupping. > > | - Is there a "last accessed date" on FAT32 partitions? > | - Does that change as McAfee reads files? > | - Shouldn't the fact that *tar* reads files also affect the date? > > The data affected IMHO should only be raised when it is changed, not > read, problem could be that because fat32 don't have a read-tag, it is > mapped to changed.. and therefore the file gets 'updated' when read. > > /Andy In other words: "Incomplete filesystem error" The other *.exe files (given total: 14) didn't make tar react... I guess it must be a "race condition" between tar and McAfee then. /Hannu E K Nevalainen, Mariefred, Sweden --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/