[BackupPC-users] Re: No way to backup a 13Gb /home directory

[Tarjei H. <ta...@nu...>]

Hi, 

On Sat, 2005-12-03 at 13:15 +0100, Tarjei Huse wrote:
> On Thu, 2005-12-01 at 10:23 +0100, Guus Houtzager wrote:
> > On Thu, 2005-12-01 at 10:05 +0100, ta...@nu... wrote:
> > [...]
> > 
> > > This is the same problem I am experiencing. My problem is also on LVM2, 
> > > running
> > > reiserfs. Any tips on how to a) increase the nr of inodes or b) check other
> > > problems would be welcome.
> >  
> > Reiser dynamically allocates inodes and by doing so has always enough
> > inodes.
> > 
> > To debug both your problems: all I can think of at this stage is try to
> > narrow it down which directory which file is causing the problems
> > (remember the buffering in the output in the logs, so you may not see
> > the actual last line or file). When you have that determined, try to
> > backup only that and if that fails, try to tcpdump and strace -p what's
> > going on and post those results here. Maybe someone can see what's going
> > on. I'm betting there's an error or bug somewhere in the
> > rsync-on-the-client vs the backuppc-rsyncp-on-the-server.
> > Please increase the rsyncloglevel of backuppc to 9 (don't know the exact
> > name on top of my head).

Did you mean the XferLogLevel or some other loglevel?

> Hi, I'm starting to think that this is actually a full disk. I've
> ordered a new one and hope that will solve the issues. Df is reporting
> the disk to be 90% full so I think that is the problem.

I just thought I'd report back that increasing disk size didn't solve
the problem - allthought it was needed :-). Also, it prooved the
importance of running stuff like this on lvm .

I'm now trying to run a new backup after setting the XferLogLevel to 9
and adding -v and --progress to the rsyncargs. Is --progress allowed
btw?

Regards,
Tarjei