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

Re: --nuke takes surprisingly long time

To: Gleb Arshinov <gleb.lists@pluron.com>
Subject: Re: --nuke takes surprisingly long time
From: Colin Percival <cperciva@tarsnap.com>
Date: Fri, 17 Jun 2011 17:25:38 -0700
Cc: tarsnap-users@tarsnap.com
In-reply-to: <BANLkTi=03cjyfBxA9jzZePcr6y_2KrtsXw@mail.gmail.com>
Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
References: <BANLkTi=03cjyfBxA9jzZePcr6y_2KrtsXw@mail.gmail.com>

On 06/17/11 17:09, Gleb Arshinov wrote:
> Is this expected?  I would have thought it would be very fast.

Depends on your definition of "surprisingly long time", I guess -- it needs to
download a list of blocks and then issue delete requests for them.  If you have
lots of data this can take a while... the total amount of bandwidth is around
0.5% of the data stored.

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

References:
- --nuke takes surprisingly long time
  - From: Gleb Arshinov <gleb.lists@pluron.com>

Prev by Date: --nuke takes surprisingly long time
Next by Date: Newbie question about "machines"
Previous by thread: --nuke takes surprisingly long time
Next by thread: Newbie question about "machines"
Index(es):
- Date
- Thread