[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Global Cache Dir Required?
- To: tarsnap-users@tarsnap.com
- Subject: Global Cache Dir Required?
- From: Mark McGranaghan <mmcgrana@gmail.com>
- Date: Sun, 6 Jun 2010 13:10:49 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=lqDVxkaCnybFpnaHBL+SuEV6DxCp5VWDzuTZIQp3RqkXNOL5FuZQW8zoQKlB8vXgS7 gFNNbKF4ysxC4Z1QSRR92E7QYxTF3fN02ZRuHAsUeSywXwD/ac3r1y19L4G4jbgrkWFF MsEKxMLIKcQRbs+U+GDi6SUXLE5pRNel/iD0U=
- Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
Hi,
Do all users of tarsnap for a particular tarsnap account effectively
have to share the same cache dir? For example, I usually use tarsnap
like `tarsnap -c -f archive-name-$timestamp archive-dir` which then
uses /usr/local/tarsnap-cache. I wanted to archive a different dir
without touching my usual cache, so I tried `tarsnap -c -f
other-archive-name-$timestamp other-archive-dir` but got:
tarsnap: Sequence number mismatch: Run --fsck
tarsnap: Error creating new archive
This happens whether or not I `mkdir other-archive-dir` before
invoking tarsnap. Am I doing something wrong here or is this a matter
of tarsnap's design? Is there any way to operate tarsnap without using
a cache dir at all?
Thanks,
Mark