summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordistix ticketing system <distix@pieni.net>2017-06-23 12:53:03 +0000
committerdistix ticketing system <distix@pieni.net>2017-06-23 12:53:03 +0000
commitd73416118bd89f0d56f8c578eeee6780d88081d4 (patch)
treee60196ff7bcfc70737b2c05f48c655e66a7dbba3
parent44c766d6193dd7b071d7ec28582a8f6c87fac664 (diff)
downloadobnam-support-distix-d73416118bd89f0d56f8c578eeee6780d88081d4.tar.gz
imported mails
-rw-r--r--tickets/5a8dabbbeb2547d4a2a2cbdad489ed4d/Maildir/new/1498222383.M325181P21602Q1.koom150
1 files changed, 150 insertions, 0 deletions
diff --git a/tickets/5a8dabbbeb2547d4a2a2cbdad489ed4d/Maildir/new/1498222383.M325181P21602Q1.koom b/tickets/5a8dabbbeb2547d4a2a2cbdad489ed4d/Maildir/new/1498222383.M325181P21602Q1.koom
new file mode 100644
index 0000000..8d0cd95
--- /dev/null
+++ b/tickets/5a8dabbbeb2547d4a2a2cbdad489ed4d/Maildir/new/1498222383.M325181P21602Q1.koom
@@ -0,0 +1,150 @@
+Return-Path: <obnam-support-bounces@obnam.org>
+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 C5A0D43160
+ for <distix@pieni.net>; Fri, 23 Jun 2017 12:51:13 +0000 (UTC)
+Received: from platypus.pepperfish.net (unknown [10.112.100.20])
+ by bagpuss.pepperfish.net (Postfix) with ESMTP id 47C6CB9B;
+ Fri, 23 Jun 2017 13:51:13 +0100 (BST)
+Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
+ by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+ id 1dOO3N-0000iu-65; Fri, 23 Jun 2017 13:51:13 +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 1dOO3M-0000ij-GX
+ for <obnam-support@obnam.org>; Fri, 23 Jun 2017 13:51:12 +0100
+Received: from mx00.igc.gulbenkian.pt ([193.137.94.10])
+ by inmail2.pepperfish.net with esmtp (Exim 4.89)
+ (envelope-from <palmeida@igc.gulbenkian.pt>) id 1dOO3K-0005qW-Mx
+ for obnam-support@obnam.org; Fri, 23 Jun 2017 13:51:12 +0100
+Received: from localhost (localhost [127.0.0.1])
+ by mx00.igc.gulbenkian.pt (Postfix) with ESMTP id F11132B6146;
+ Fri, 23 Jun 2017 13:51:00 +0100 (WEST)
+X-Virus-Scanned: Debian amavisd-new at igc.gulbenkian.pt
+Received: from mx00.igc.gulbenkian.pt ([127.0.0.1])
+ by localhost (igc.gulbenkian.pt [127.0.0.1]) (amavisd-new, port 10024)
+ with LMTP id 98SZlTUWfP-W; Fri, 23 Jun 2017 13:51:00 +0100 (WEST)
+Received: from mx03 (mx03.igc.gulbenkian.pt [192.168.50.13])
+ by mx00.igc.gulbenkian.pt (Postfix) with ESMTP id 2FBCF2B610F;
+ Fri, 23 Jun 2017 13:51:00 +0100 (WEST)
+Received: from localhost (localhost [127.0.0.1])
+ by mx03 (Postfix) with ESMTP id 214ED60194;
+ Fri, 23 Jun 2017 13:51:00 +0100 (WEST)
+Received: from mx03 ([127.0.0.1])
+ by localhost (mx03.igc.gulbenkian.pt [127.0.0.1]) (amavisd-new, port 10024)
+ with ESMTP id ySLnUJmPqYaH; Fri, 23 Jun 2017 13:50:59 +0100 (WEST)
+Received: from hp0913024 (fw1dmz.igc.gulbenkian.pt [192.168.50.3])
+ by mx03 (Postfix) with ESMTPSA id 5EF286002A;
+ Fri, 23 Jun 2017 13:50:58 +0100 (WEST)
+Message-ID: <1498222257.32724.1.camel@igc.gulbenkian.pt>
+From: Paulo Almeida <palmeida@igc.gulbenkian.pt>
+To: Lars Wirzenius <liw@liw.fi>
+Date: Fri, 23 Jun 2017 13:50:57 +0100
+In-Reply-To: <20170621185929.hwrn4qxomzzobofh@liw.fi>
+References: <1498070485.18005.3.camel@igc.gulbenkian.pt>
+ <20170621185929.hwrn4qxomzzobofh@liw.fi>
+Organization: Instituto Gulbenkian de =?ISO-8859-1?Q?Ci=EAncia?=
+Content-Type: text/plain; charset="UTF-8"
+X-Mailer: Evolution 3.22.6-1
+Mime-Version: 1.0
+Content-Transfer-Encoding: 8bit
+X-Pepperfish-Transaction: 52d3-1b62-c201-1441
+X-Spam-Score: -3.4
+X-Spam-Score-int: -33
+X-Spam-Bar: ---
+X-Scanned-By: pepperfish.net, Fri, 23 Jun 2017 13:51:12 +0100
+X-Spam-Report: Content analysis details: (-3.4 points)
+ pts rule name description
+ ---- ---------------------- --------------------------------------------------
+ -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
+ domain -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
+ [193.137.94.10 listed in wl.mailspike.net]
+ -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
+ [score: 0.0000]
+ -1.5 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium
+ trust [193.137.94.10 listed in list.dnswl.org]
+ -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
+X-ACL-Warn: message may be spam
+X-Scan-Signature: 058b39b569832a6e6ccbf5e13e8e5099
+Cc: obnam-support@obnam.org
+Subject: Re: obnam forget - keeping older backups and deleting the most
+ recent
+X-BeenThere: obnam-support@obnam.org
+X-Mailman-Version: 2.1.5
+Precedence: list
+List-Id: Obnam backup software discussion <obnam-support-obnam.org>
+List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=unsubscribe>
+List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
+List-Post: <mailto:obnam-support@obnam.org>
+List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
+List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
+ <mailto:obnam-support-request@obnam.org?subject=subscribe>
+Sender: obnam-support-bounces@obnam.org
+Errors-To: obnam-support-bounces@obnam.org
+
+I did run into a hitch while trying to delete generations. As I said in
+the original message, I exceeded the storage system quota while backing
+up. When I ran:
+
+obnam forget <generation>
+
+it attempted to create a temporary file (or directory) in the
+repository folder and it failed with "Disk quota exceeded". I saw in
+the man page that obnam accepts certain standard environment variables,
+so I tried:
+
+TMPDIR=/tmp obnam forget <generation>
+
+but that made no difference. I was going to ask my IT department to
+temporarily raise my quota, but I browsed a bit and found some old
+stuff I could delete. I'm running obnam forget now and already reduced
+usage from 155 GB to 152 GB with the first five generations (there are
+70+ checkpoints), so I expect the rest of the process to go well.
+
+As further reflection, I also tried to look in the manual for something
+that might give me the chunks of the relevant generations, so I could
+delete them manually, but of course that would involve making sure
+those chunks were not used for any other files. I suppose one
+alternative would be to copy the whole repository to another computer,
+run obnam forget pointing to that repository and then move it back to
+the storage server, but that would take a while. (I'm just thinking
+about what I could have done if I didn't have the option of deleting
+other files or raising the quota).
+
+Thanks,
+Paulo
+
+On Wed, 2017-06-21 at 21:59 +0300, Lars Wirzenius wrote:
+> On Wed, Jun 21, 2017 at 07:41:25PM +0100, Paulo Almeida wrote:
+> > Hi,
+> >
+> > I'm using obnam for my /home backup and due to a mistake in the
+> > excludes (forgot the commas when adding a couple of new
+> > directories), I
+> > backed up a lot of things I didn't want to, and the storage system
+> > ran
+> > out of quota. I would like to delete only the most recent backup,
+> > and
+> > keep everything else, but that doesn't seem to be possible with
+> > obnam
+> > forget's keep parameter. Is that right? If so, is there an
+> > alternative?
+> > Would it be feasible/desirable to add a '+' modifier to the keep
+> > parameter, like in the mtime of find, to only keep generations
+> > older
+> > than x and not more recent?
+>
+> You can use "obnam generations" to list all generations, and make
+> note
+> of the generation ids (first column). Then run "obnam forget 1 2 3"
+> to
+> delete generations with ids 1, 2, 3. I hope that helps.
+>
+
+_______________________________________________
+obnam-support mailing list
+obnam-support@obnam.org
+http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org