gregrwm wrote at about 19:05:18 -0500 on Tuesday, June 14, 2022:
> offhand i'm not really seeing why an interrupt would result in the loss of
> a prior backup directory. i'd be surprised to learn that a prior backup is
> ever moved or renamed and thus subject to loss if interrupted, but what
On Tue, Jun 14, 2022 at 5:25 PM G.W. Haywood via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> Hi there,
>
> On Tue, 14 Jun 2022, gregrwm wrote:
> > ... interrupted BackupPC_dump. on the next invocation i got:
> > 2022-06-12 21:35:02 Serious error: last backup
> >
Hi there,
On Tue, 14 Jun 2022, gregrwm wrote:
... interrupted BackupPC_dump. on the next invocation i got:
2022-06-12 21:35:02 Serious error: last backup
/var/lib/backuppc/pc/avocado/32 directory doesn't exist!!! Need to remove
back to last filled backup
2022-06-12 21:35:02 Deleting backup
gregrwm wrote at about 19:24:17 -0500 on Monday, June 13, 2022:
> i hadn't prepared my config quite as i'd intended, and expected a rather
> long wait, so i interrupted BackupPC_dump.
> on the next invocation i got:
> 2022-06-12 21:35:02 Serious error: last backup
>
i hadn't prepared my config quite as i'd intended, and expected a rather
long wait, so i interrupted BackupPC_dump.
on the next invocation i got:
2022-06-12 21:35:02 Serious error: last backup
/var/lib/backuppc/pc/avocado/32 directory doesn't exist!!! Need to remove
back to last filled backup
Dear Holger,
> f...@igh.de wrote on 2018-03-08 16:59:37 +0100 [Re: [BackupPC-users] Serious
> error: last backup ... directory doesn't exist!!! - reason found]:
> > [...]
> > Meanwhile I found the reason: the partition ran out of inodes. As you
> > wrote under "
On 2018-03-13 16:33, Holger Parplies wrote:
My first thought is to avoid the issue altogether by using a file
system
that doesn't statically allocate inodes (e.g. XFS or reiserfs, the
latter
I wouldn't recommend for other reasons, though; I don't know about
ext4,
btrfs and ZFS, but my guess
Hi,
f...@igh.de wrote on 2018-03-08 16:59:37 +0100 [Re: [BackupPC-users] Serious
error: last backup ... directory doesn't exist!!! - reason found]:
> [...]
> Meanwhile I found the reason: the partition ran out of inodes. As you
> wrote under "How much disk space do I need?&qu
One of the more challenging aspects of this is the number of inodes that
BackupPC consumes
is directly related to how many inodes you're backing up. If I recall
correctly, in
BackupPC 4.x, each 'filled' backup will use 2 inodes per object backed up in
addition to
the inode consumed by the
On 3/8/2018 6:59 PM, f...@igh.de wrote:
Craig,
again I return to my issue "No space left on device".
Meanwhile I found the reason: the partition ran out of inodes. As you
wrote under "How much disk space do I need?" one has to have "plenty
of inodes". But what does that mean?
May I ask the
Craig,
again I return to my issue "No space left on device".
Meanwhile I found the reason: the partition ran out of inodes. As you
wrote under "How much disk space do I need?" one has to have "plenty
of inodes". But what does that mean?
May I ask the following:
- in the "General Server
Dear Craig,
> Thanks for the additional info, but I can't explain the behavior your are
> seeing. Sending to the user-list to see if others have suggestions.
>
> BackupPC seems to be unable to create directories and files below
> /vol/bpc4/BackupPC. The "No space left on device" errno seems
Torsten,
Thanks for the additional info, but I can't explain the behavior your are
seeing. Sending to the user-list to see if others have suggestions.
BackupPC seems to be unable to create directories and files below
/vol/bpc4/BackupPC. The "No space left on device" errno seems inconsistent
Other things to check include:
- is the file system full? (df) - you did say it was only 65% full, so
that should be ok
- have you run out of inodes? (df -i)
If you can't directly see some problem with the file system the next step
is to stop backuppc, unmount the file system and run
Here are a few things to check:
- can you manually create files and directories below /vol/bpc4/BackupPC
as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir foo;
rmdir foo; touch foobar; rm foobar")
- is the file system mounted readonly?
- has the backuppc user
Dear BackupPC Users,
I am running BackupPC-4.1.3 for several months without problems
(really a great piece of software).
About a week ago a strange type of error occured and keeps staying,
which I cannot understand. The error messages are like this ("fs" is
the name of one of my systems to be
16 matches
Mail list logo
