[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New data reported too big

To: Andy Lutomirski <luto@amacapital.net>
Subject: Re: New data reported too big
From: Colin Percival <cperciva@tarsnap.com>
Date: Sun, 06 Oct 2013 15:46:53 -0700
Cc: Yonatan Broza <yonatan@cuppcomputing.com>, tarsnap-users@tarsnap.com, Mark Kaplan <mkaplan@cuppcomputing.com>
In-reply-to: <CALCETrXzsdx33yCJ4vXy==MJHGS0LrTir3VfCXyW-P=VcTzJTg@mail.gmail.com>
References: <CAO-ciensFSMgXK12yS3UDppyJ+KOz--iPtLjVaFFF2vvXuXyTQ@mail.gmail.com> <524862FC.5000707@tarsnap.com> <CALCETrXzsdx33yCJ4vXy==MJHGS0LrTir3VfCXyW-P=VcTzJTg@mail.gmail.com>

On 10/06/13 14:26, Andy Lutomirski wrote:
> On Sun, Sep 29, 2013 at 10:27 AM, Colin Percival <cperciva@tarsnap.com> wrote:
>> Tarsnap stores a 512-byte tar header for each file, and this header
>> includes the file modification time. 22,000 files x 512 bytes/file = 11.2
>> MB, so this looks like the reason for the new data you're seeing.
>
> Aha!  Is there an easy way to turn that off?  I archive a fair amount
> of autogenerated data, and the timestamps are completely worthless as
> far as I'm concerned.

No way to turn it off.  The best I can suggest is to compare your old and
new autogenerated data and only install the new data if it's different.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid

Follow-Ups:
- Re: New data reported too big
  - From: Andy Lutomirski <luto@amacapital.net>

References:
- New data reported too big
  - From: Yonatan Broza <yonatan@cuppcomputing.com>
- Re: New data reported too big
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: New data reported too big
  - From: Andy Lutomirski <luto@amacapital.net>

Prev by Date: Re: New data reported too big
Next by Date: Re: Tarsnap logo contest
Previous by thread: Re: New data reported too big
Next by thread: Re: New data reported too big
Index(es):
- Date
- Thread