Saturn2888 wrote:
> All of these logs are in BackupPC in the LOG area determined for each host.
>
Both remote and local errors are collected there. Post a few of the most
common
types of entries.
--
Les Mikesell
lesmikes...@gmail.com
---
All of these logs are in BackupPC in the LOG area determined for each host.
Les Mikesell wrote:
> On 8/9/2010 4:54 PM, Saturn2888 wrote:
>
> > Did a fsck on the entire filesystem, no fix. They are from any rsync or
> > rsyncd operation. I don't know what you mean by from remote rsync. Is that
On 8/9/2010 4:54 PM, Saturn2888 wrote:
> Did a fsck on the entire filesystem, no fix. They are from any rsync or
> rsyncd operation. I don't know what you mean by from remote rsync. Is that an
> application or are you talking about the protocol? I think I'm missing some
> kind of related underst
Did a fsck on the entire filesystem, no fix. They are from any rsync or rsyncd
operation. I don't know what you mean by from remote rsync. Is that an
application or are you talking about the protocol? I think I'm missing some
kind of related understanding here.
Les Mikesell wrote:
> On 8/9/201
On 8/9/2010 2:59 PM, Saturn2888 wrote:
> Naw, the excluding is working just fine. Those files popping up aren't
> excluded. In one case they were, but I fixed that; it was just one entry
> which was broken.
>
So what do some of the other log entries say? And if they are from the
remote rsync,
Naw, the excluding is working just fine. Those files popping up aren't
excluded. In one case they were, but I fixed that; it was just one entry which
was broken.
Les Mikesell wrote:
> On 8/9/2010 12:27 PM, Saturn2888 wrote:
>
> > Logs are now anywhere from 16MB to 30MB. The problem is only gro
On 8/9/2010 12:27 PM, Saturn2888 wrote:
> Logs are now anywhere from 16MB to 30MB. The problem is only growing, and I
> don't know why. If those are rsync errors, why am I seeing them only since
> the upgrade to Lucid? In parts of my findings, they're benign, but the log
> sizes being that large
Logs are now anywhere from 16MB to 30MB. The problem is only growing, and I
don't know why. If those are rsync errors, why am I seeing them only since the
upgrade to Lucid? In parts of my findings, they're benign, but the log sizes
being that large even compressed is pretty scary since they were
Craig Barratt wrote:
> Saturn2888 writes:
>
>
> > To make it easier for people to know what I'm talking about, here are the
> > errors I'm getting in my logs. It's a bunch of things like these for
> > different folders on different hosts.
> > 2010-07-28 02:40:03 ERROR: opendir
> > (/var/lib/b
Saturn2888 writes:
> To make it easier for people to know what I'm talking about, here are the
> errors I'm getting in my logs. It's a bunch of things like these for
> different folders on different hosts.
> 2010-07-28 02:40:03 ERROR: opendir
> (/var/lib/backuppc/pc/main/174/ffull-drive/fusr/fl
fsck finished with no problems. Here's what it is, those errors are coming up
when they should not. The specific case I was looking at, I had rsync exclude
some directories and recently changed it thinking it wasn't excluding them
(oops). So the errors shouldn't have even appeared in the first p
I don't think the RAM is bad, but I can do a check on it. The directories no
longer exist but I swear they had to have. After a lot of observation, it's
creating new directories and after 2 full backups, the errors stop (duh,
because it's not looking back an extra full backup when rsyncing). I a
On 8/4/2010 8:23 AM, Saturn2888 wrote:
> An update, it's doing it now for newer files too and my log files are only
> growing in size. What's with ext4? Is there a way to check if something's
> amok? Fsck says the file system is clean.?
'Clean' means it was unmounted before the last shutdown, no
On 8/4/2010 8:57 AM, Saturn2888 wrote:
> To make it easier for people to know what I'm talking about, here are the
> errors I'm getting in my logs. It's a bunch of things like these for
> different folders on different hosts.
> 2010-07-28 02:40:03 ERROR: opendir
> (/var/lib/backuppc/pc/main/174/
To make it easier for people to know what I'm talking about, here are the
errors I'm getting in my logs. It's a bunch of things like these for different
folders on different hosts.
2010-07-28 02:40:03 ERROR: opendir
(/var/lib/backuppc/pc/main/174/ffull-drive/fusr/flib/fperl5/fauto/fText/fCSV_XS)
An update, it's doing it now for newer files too and my log files are only
growing in size. What's with ext4? Is there a way to check if something's amok?
Fsck says the file system is clean.?
Saturn2888 wrote:
> Not gigabytes, it was megabytes, but after searching this, either those files
> ne
Not gigabytes, it was megabytes, but after searching this, either those files
never did get backed up or something else happened to them. Strangely, even
through all of this the pool size has only grown 3GB since I first turned it on
again. I'm very confused.
Missing files should lower the tota
I shrunk an ext3 partition and dd'd it over into an LVM2 partition on a Linux
Software RAID1 then I moved the /var/lib/backuppc out and deleted the rest of
the drive contents bc I'd already copied those manually. Then I upgraded the
file system to ext4 by doing some kinda tune2fs commands to ma
18 matches
Mail list logo
