Since there's nothing of interest in the XferLOG file, I'd recommend
running BackupPC_dump from the command-line with the -v option. That
should copy all log messages to stdout so you should see them in real
time. First make sure there are no backups running on HOST (where HOST is
kestrel or loca
Hi there,
Thanks for your reply.
On Thu, 20 Sep 2018, Craig Barratt wrote:
First, this error message looks like just a bug in the message text: it
shouldn't be concatenating those paths:
> RmTreeQuietInner:
> /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> isn't a d
First, this error message looks like just a bug in the message text: it
shouldn't be concatenating those paths:
RmTreeQuietInner:
> /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> isn't a directory (while removing
> /var/lib/backuppc/pc/kestrel/268/X/f.cache)
Back
On 2018-09-19 03:52, G.W. Haywood via BackupPC-users wrote:
Hello again all,
On Tue, 18 Sep 2018, Michael Stowe wrote:
On Mon, 17 Sep 2018, G.W. Haywood wrote:
I suspect that this is a fault in BackupPC_backupDelete ...
RmTreeQuietInner seems to be seeing some sort of bowdlerization
...
RmTre
Hello again all,
On Tue, 18 Sep 2018, Michael Stowe wrote:
On Mon, 17 Sep 2018, G.W. Haywood wrote:
I suspect that this is a fault in BackupPC_backupDelete ...
RmTreeQuietInner seems to be seeing some sort of bowdlerization
...
RmTreeQuietInner:
/mnt/3TLV/backuppc/pc/kestrel/268//var/lib/back
>
> >>> ... BackupPC appears to think that it has now used 5TB of a 3TB
> >>> disc and the claimed usage is growing. ...
>
> ... and growing. It's now claiming 8.5TB used by the pool. Pretty
> soon the claimed pool usage will exceed the total storage used by all
> the hosts that are being backed
On 2018-09-17 12:15, G.W. Haywood via BackupPC-users wrote:
Hello again all,
[Replying to myself here to try to get the thread back on topic.]
Thank you!
On Mon, 17 Sep 2018, G.W. Haywood wrote:
... I suspect that this is a fault in BackupPC_backupDelete ...
8<--
Hello again all,
[Replying to myself here to try to get the thread back on topic.]
On Mon, 17 Sep 2018, G.W. Haywood wrote:
... I suspect that this is a fault in BackupPC_backupDelete ...
8<--
BackupPC_backupDelete debug ou
On 2018-09-16 11:59, Mike Hughes wrote:
Michael,
Condescending and belittling treatment of others in this list is not
the norm. Your personal attacks are unwarranted and unhelpful.
I certainly didn't mean anything that way, and let me apologize should
anybody have taken anything that way. My
s necessary to fit the situation.
I hope this helps.
Sincerely,
Mike
From: Michael Stowe
Sent: Sunday, September 16, 2018 11:39:51 AM
To: General list for user discussion, questions and support
Cc: G.W. Haywood
Subject: Re: [BackupPC-users] BackupPC 4.2.1 appare
On 2018-09-16 05:27, G.W. Haywood via BackupPC-users wrote:
Once again, thank you for your input. Do consider some restraint.
That's fair. Consider the context: you've already admitted to breaking
BackupPC after an upgrade and instead of methodically going through the
steps of getting it
Hi there,
On Sat, 15 Sep 2018, Michael Stowe wrote:
... 4.2.1 seemed to be eating a LOT more disc space than V3.x ...
tried used BackupPC_backupDelete to delete some cruft ...
And I used "rm -r *" to list the contents of a directory.
Thanks very much for your reply, and if you ever find you
On 2018-09-14 04:37, G.W. Haywood via BackupPC-users wrote:
Hi there,
About a month ago I made the elementary mistake of upgrading my backup
server from Debian Jessie to Debian Stretch. Just about everything
broke.
The biggest concern was the backups themselves. The upgrade changed
BackupPC
Hi there,
About a month ago I made the elementary mistake of upgrading my backup
server from Debian Jessie to Debian Stretch. Just about everything broke.
The biggest concern was the backups themselves. The upgrade changed
BackupPC from version 3.3.0, which seemed to have been working fine for
14 matches
Mail list logo
