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

Re: sequence number mismatch

To: Michael Stevens <mstevens@etla.org>
Subject: Re: sequence number mismatch
From: Colin Percival <cperciva@tarsnap.com>
Date: Thu, 02 Jun 2011 07:33:36 -0700
Cc: tarsnap-users@tarsnap.com
In-reply-to: <20110602085558.GA9724@ceres.etla.org>
Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
References: <20110601211025.GA23004@ceres.etla.org> <4DE734DE.6090601@tarsnap.com> <20110602085558.GA9724@ceres.etla.org>

On 06/02/11 01:55, Michael Stevens wrote:
> On further testing, I seem to have lost the ability to create new
> archives even with a clean cache:
> 
> root@ceres:~# ./backup.sh
> Directory /usr/local/tarsnap-cache created for "--cachedir /usr/local/tarsnap-cache"
> tarsnap: Sequence number mismatch: Run --fsck
> tarsnap: Error creating new archive

This makes sense.  A missing cache directory (or an empty directory newly
created by tarsnap) is absolutely not going to be in sync with the server
state.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid

References:
- sequence number mismatch
  - From: Michael Stevens <mstevens@etla.org>
- Re: sequence number mismatch
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: sequence number mismatch
  - From: Michael Stevens <mstevens@etla.org>

Prev by Date: Re: tarsnap-keygen script usage
Next by Date: Re: sequence number mismatch
Previous by thread: Re: sequence number mismatch
Next by thread: Sequence number mismatch
Index(es):
- Date
- Thread