X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=cBiRPFVosjPMYIT3
	XERsp6BL27FTUJF60FN5l+vM5ejiXyrQkDEEO24/7pC1+epgR9ySjxeVHF+4r0mK
	K2BcGlaEiE642LKIYpO/tCs7Gniej3wSNe9jHvFbHdhV+o2h3QsN37NTIyzSlvFA
	KH+DdCYsEWw4KBzD3ztnBhAiP6g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=dRijRS/cHNhZ7scAJjQT6p
	cdT1g=; b=j7H6/N06CCGepUN3Kwv4B9qmSs+GpUxcaMe9R3POPs+jPthc1HLOBZ
	ycjxkFDQ9liNuL9DzYBz3SeNIkEn53+EvR0DU08uEA8tE5AkPuv1r69IhA+UoB/G
	EGcTB325kqYqTkT0cMgbLUuegSA5b1iOsnOF+LRzhu7tuxPc6pbEI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=company, meet, commercial, wish
X-HELO: mail-wm0-f46.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:subject:to:references:from:message-id:date         :user-agent:mime-version:in-reply-to:content-transfer-encoding;        bh=HcSbMbuYkIwwceN4a5H2j51eXxCS4UDeO4Rl5EyeIE0=;        b=LOuWIYqbuk3slY0ZxvDytIPWOOKN3bOwfTl4UJoGBzuYOD45x44GPACY8qEbezd+ch         Prf8q3vWcO+YJdMzK6fbCEhZ8k4Dl5gZKXx6+i6KLh3ypK4OTRzYGj6MX52BWRdyw/PG         PdeHEp1N6lz8Sxwk0z8QZfaKv9TgG3dPBZiOssdLP0b/IgJacXEq4VZACIukiOg2G+/A         TkcAt2TeOP5AWGpXrxo6BgzJpg7AM/FXRGIxB4gw+MKWq38IYLuVzBkjyPNdEbXNsErZ         CZ6wTBcD7hqNRgcv1Dma7GyczuQDxW51jc3nbbqZRqg1x5nx4f1gOYC6tsjuJib+9JO4         Zgbw==
X-Gm-Message-State: ALyK8tLGJqtu/+Yhc67Wl/xIugkui6WOyz7/Sbajcx1GrgNaxBktY3Fs/jeLz534zpvqAg==
X-Received: by 10.28.230.87 with SMTP id d84mr14238946wmh.50.1464017729940;        Mon, 23 May 2016 08:35:29 -0700 (PDT)
Subject: =?UTF-8?Q?Re:_tar_incremental_backups_and_ctime=e2=80=8f_problem?=
To: cygwin AT cygwin DOT com
References: <CAOKAGPP0o6vV2KTpfs4M0DyqwHA3pVw-+xkwLmjyWpAFthbA+A AT mail DOT gmail DOT com> <9fdf98cf-e3d1-e453-1c98-2c206afe81c9 AT gmail DOT com> <CAOKAGPOzSYkmFRJazgQMwjUCKsKaBbE9gcVAdNnNvYUkmc=9Bw AT mail DOT gmail DOT com> <09f604cd-61df-e0c7-b313-1dcf1ef59b4e AT gmail DOT com> <CAOKAGPMHEiNLW3makusvvx2E7V9etjA+YPUMDh56=N42wmtLYA AT mail DOT gmail DOT com> <574313B3 DOT 3090703 AT redhat DOT com> <CAOKAGPOVnU1Lr2od-UbtRAeZHFKjnNC2jOmmGouVotSYMxbokw AT mail DOT gmail DOT com>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <b2009993-f09a-c07f-f524-34266334c151@gmail.com>
Date: Mon, 23 May 2016 17:35:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAOKAGPOVnU1Lr2od-UbtRAeZHFKjnNC2jOmmGouVotSYMxbokw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 23/05/2016 16:57, x y wrote:
>> mtime is fakeable, ctime is not.  Using only mtime makes it likely that
>> your incremental backup will miss files.  I don't have any good reason
>> to differ from upstream behavior here.
>
> Hi Eric,
>
> The problem is not faking time stamps. Even commercial Windows backup
> programs are checking the modification time to identify the modified
> files.
>
> Consider that you have a lot of files opened and closed without any
> modification in your company. Because of the priority of the ctime
> time stamp, reintroducing all of those files to the incremental backup
> does not make any sense. tar has also the capacity to create
> differential backups with the condition of taking care of the snapshot
> file. The ctime issue can result in unnecessarily big differential
> backups filled with unmodified files.
>
> Cygwin tar can be a good  alternative for Windows users to do
> differential \ incremental backups but the ctime problem must be
> solved.
>

It is always possible to create file list with find and use that
to tar whatever using --files-from=FILE option

I don't see the need to change tar behaviour to meet your wish.

Regards
Marco








--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple