Nate wrote:
> Yeah, I doubt very much it's a backuppc issue, sorry if I may have
> implied that. I'm fairly confident it's a ext3/driver issue. But as
> this popped up when we began using backuppc I suspect it may have to
> do with the massive quantities of files and had hoped another
> backu
Yeah, I doubt very much it's a backuppc issue, sorry if I may have
implied that. I'm fairly confident it's a ext3/driver issue. But as
this popped up when we began using backuppc I suspect it may have to
do with the massive quantities of files and had hoped another
backuppc may have encounter
Yeah I can't see how this is a backuppc issue
On Thu, Mar 5, 2009 at 11:07 AM, Chris Robertson wrote:
> Nate wrote:
> > We seem to be routinely having this issue where the server backuppc
> > is running on throws a kernel panic and thus hard locks the
> > machine. It's completely random, someti
Nate wrote:
> We seem to be routinely having this issue where the server backuppc
> is running on throws a kernel panic and thus hard locks the
> machine. It's completely random, sometimes happens daily, sometimes
> we can have a lucky 2-3 weeks without a lockup. I've taken a
> screenshot and
We seem to be routinely having this issue where the server backuppc
is running on throws a kernel panic and thus hard locks the
machine. It's completely random, sometimes happens daily, sometimes
we can have a lucky 2-3 weeks without a lockup. I've taken a
screenshot and posted it here:
http
Hi
is there a way to check for corrupted files in backuppc's pools?
If my bakcuppc server hangs or gets reseted or other bad things.. at
next boot it does an fsck of the filesystems and, suppose, fsck puts
some file in lost+found..
Is there a way to discover wich backups are to be considered co
