Return-Path: X-Original-To: distix@pieni.net Delivered-To: distix@pieni.net Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16]) by pieni.net (Postfix) with ESMTPS id B95AA4460C for ; Mon, 19 Jun 2017 14:36:16 +0000 (UTC) Received: from platypus.pepperfish.net (unknown [10.112.100.20]) by bagpuss.pepperfish.net (Postfix) with ESMTP id 948DCBA0; Mon, 19 Jun 2017 15:36:16 +0100 (BST) Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net) by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) id 1dMxmq-000726-GF; Mon, 19 Jun 2017 15:36:16 +0100 Received: from yaffle.pepperfish.net ([88.99.213.221] helo=inmail2.pepperfish.net) by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian)) id 1dMxmo-00071r-Ly for ; Mon, 19 Jun 2017 15:36:14 +0100 Received: from davros.xk7.net ([46.43.0.197]) by inmail2.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1dMxmm-0004WG-DT for obnam-dev@obnam.org; Mon, 19 Jun 2017 15:36:14 +0100 Received: from [IPv6:2a02:8011:1f:0:a453:5e1b:d606:8355] (unknown [IPv6:2a02:8011:1f:0:a453:5e1b:d606:8355]) by davros.xk7.net (Postfix) with ESMTPSA id 4B167E647D for ; Mon, 19 Jun 2017 15:36:05 +0100 (BST) To: obnam-dev@obnam.org References: <20170619143239.egma6t52nudu6jqq@liw.fi> From: Paul Waring Message-ID: Date: Mon, 19 Jun 2017 15:36:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170619143239.egma6t52nudu6jqq@liw.fi> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pepperfish-Transaction: 2fe6-d9e4-b2fd-8e3f X-Spam-Score: -2.3 X-Spam-Score-int: -22 X-Spam-Bar: -- X-Scanned-By: pepperfish.net, Mon, 19 Jun 2017 15:36:14 +0100 X-Spam-Report: Content analysis details: (-2.3 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.3 PPF_FROM_UK RBL: A Received line involves an address from the UK [46.43.0.197 listed in gb.country.dnsbl.rjek.com] -0.5 PPF_USER_AGENT User-Agent: exists 0.4 PPF_WINDOWS_CHARSET Content-Type is in a Windows-* charset -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-ACL-Warn: message may be spam X-Scan-Signature: e22476795c0c271ab9cf3b1ad5ae1506 Subject: Re: More informative Obnam progress reporting X-BeenThere: obnam-dev@obnam.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Obnam development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: obnam-dev-bounces@obnam.org Errors-To: obnam-dev-bounces@obnam.org X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 On 19/06/17 15:32, Lars Wirzenius wrote: > It struck me the other day that it would be nice if Obnam could give > more progress feedback reporting: > > * position in current file: some files are very large and it taks a > long time to check them completely > > * how much duplicate data is NOT uploaded in this run > > * how far in the backup we are, compared to previous generatation > > * momentary upload speed, both raw and "effective" (chunk data only) > > What do others think? This would definitely be useful, although the other 'progress' area that I think could be improved is when attempting to mount for restoring. If you have a lot of generations (>500 did it for me) then obnam sits there with no progress indication and you have no idea whether it's working, stuck in a loop, hung etc. -- Paul Waring Freelance consultant https://www.pwaring.com _______________________________________________ obnam-dev mailing list obnam-dev@obnam.org http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org