From: Kimball L. <ki...@mi...> - 2008-02-27 18:29:15
|
I've recently had to move my backuppc filesystem from one machine to another. My machines are all backing up just fine, I'm able to see all my old backups and restore files from them with no problem.. however, my pool size is reporting as 0MB. I checked the filesystem, and the size of the pool directory is in fact 0. Here is some info from the shell: root@jake:/mnt/plump/backuppc# du -sh pool 0 pool root@jake:/mnt/plump/backuppc# ls -la total 4 drwxr-x--- 9 backuppc backuppc 240 2008-02-27 10:37 . drwxr-xr-x 5 root root 104 2008-02-19 12:55 .. drwxr-x--- 12 root root 288 2008-02-19 11:27 cpool drwxr-x--- 2 backuppc root 128 2007-07-28 03:00 log drwx------ 2 backuppc root 48 2007-07-27 16:10 Mail drwxr-x--- 9 backuppc root 272 2008-02-26 15:26 pc drwxr-x--- 2 backuppc root 48 2007-05-20 15:14 pool -rw------- 1 backuppc root 812 2007-07-27 16:19 sent drwx------ 2 backuppc root 200 2008-02-20 07:37 .ssh drwxr-x--- 2 backuppc backuppc 48 2008-02-27 10:50 trash root@jake:/mnt/plump/backuppc# du -sh cpool 1.6G cpool I notice that the cpool directory is owned by root. Should it be owned by the backuppc user instead? Thanks! -- Kimball |
From: Les M. <le...@fu...> - 2008-02-27 18:46:20
|
Kimball Larsen wrote: > I've recently had to move my backuppc filesystem from one machine to > another. My machines are all backing up just fine, I'm able to see > all my old backups and restore files from them with no problem.. > however, my pool size is reporting as 0MB. I checked the filesystem, > and the size of the pool directory is in fact 0. > > Here is some info from the shell: > > root@jake:/mnt/plump/backuppc# du -sh pool > 0 pool > root@jake:/mnt/plump/backuppc# ls -la > total 4 > drwxr-x--- 9 backuppc backuppc 240 2008-02-27 10:37 . > drwxr-xr-x 5 root root 104 2008-02-19 12:55 .. > drwxr-x--- 12 root root 288 2008-02-19 11:27 cpool > drwxr-x--- 2 backuppc root 128 2007-07-28 03:00 log > drwx------ 2 backuppc root 48 2007-07-27 16:10 Mail > drwxr-x--- 9 backuppc root 272 2008-02-26 15:26 pc > drwxr-x--- 2 backuppc root 48 2007-05-20 15:14 pool > -rw------- 1 backuppc root 812 2007-07-27 16:19 sent > drwx------ 2 backuppc root 200 2008-02-20 07:37 .ssh > drwxr-x--- 2 backuppc backuppc 48 2008-02-27 10:50 trash > root@jake:/mnt/plump/backuppc# du -sh cpool > 1.6G cpool > > > I notice that the cpool directory is owned by root. Should it be > owned by the backuppc user instead? Yes, it must be writable by the backuppc user. Your logs are probably full of "unable to link" errors. -- Les Mikesell le...@fu... |
From: Kimball L. <ki...@mi...> - 2008-02-27 20:03:25
|
On Feb 27, 2008, at 11:49 AM, Les Mikesell wrote: > Kimball Larsen wrote: >> I've recently had to move my backuppc filesystem from one machine >> to another. My machines are all backing up just fine, I'm able to >> see all my old backups and restore files from them with no >> problem.. however, my pool size is reporting as 0MB. I checked >> the filesystem, and the size of the pool directory is in fact 0. >> Here is some info from the shell: >> root@jake:/mnt/plump/backuppc# du -sh pool >> 0 pool >> root@jake:/mnt/plump/backuppc# ls -la >> total 4 >> drwxr-x--- 9 backuppc backuppc 240 2008-02-27 10:37 . >> drwxr-xr-x 5 root root 104 2008-02-19 12:55 .. >> drwxr-x--- 12 root root 288 2008-02-19 11:27 cpool >> drwxr-x--- 2 backuppc root 128 2007-07-28 03:00 log >> drwx------ 2 backuppc root 48 2007-07-27 16:10 Mail >> drwxr-x--- 9 backuppc root 272 2008-02-26 15:26 pc >> drwxr-x--- 2 backuppc root 48 2007-05-20 15:14 pool >> -rw------- 1 backuppc root 812 2007-07-27 16:19 sent >> drwx------ 2 backuppc root 200 2008-02-20 07:37 .ssh >> drwxr-x--- 2 backuppc backuppc 48 2008-02-27 10:50 trash >> root@jake:/mnt/plump/backuppc# du -sh cpool >> 1.6G cpool >> I notice that the cpool directory is owned by root. Should it be >> owned by the backuppc user instead? > > Yes, it must be writable by the backuppc user. Your logs are > probably full of "unable to link" errors. > Yeah, I've been getting stuff like this: 2008-02-27 11:51:16 BackupPC_link got error -4 when calling MakeFileLink( .... I've changed the permissions... how soon should I expect to see some items wind up in the pool? Thanks! -- Kimball |
From: Les M. <le...@fu...> - 2008-02-27 20:08:36
|
Kimball Larsen wrote: > >>> I notice that the cpool directory is owned by root. Should it be >>> owned by the backuppc user instead? >> Yes, it must be writable by the backuppc user. Your logs are >> probably full of "unable to link" errors. >> > > Yeah, I've been getting stuff like this: > 2008-02-27 11:51:16 BackupPC_link got error -4 when calling > MakeFileLink( .... > > I've changed the permissions... how soon should I expect to see some > items wind up in the pool? > They should be linked during/after each backup run. You won't see much space benefit from the pooling until your old archives where the link attempt failed are expired, though. -- Les Mikesell les...@gm... |
From: Kimball L. <ki...@mi...> - 2008-02-27 20:15:20
|
On Feb 27, 2008, at 1:11 PM, Les Mikesell wrote: > Kimball Larsen wrote: >>>> I notice that the cpool directory is owned by root. Should it >>>> be owned by the backuppc user instead? >>> Yes, it must be writable by the backuppc user. Your logs are >>> probably full of "unable to link" errors. >>> >> Yeah, I've been getting stuff like this: >> 2008-02-27 11:51:16 BackupPC_link got error -4 when calling >> MakeFileLink( .... >> I've changed the permissions... how soon should I expect to see >> some items wind up in the pool? > > They should be linked during/after each backup run. You won't see > much space benefit from the pooling until your old archives where > the link attempt failed are expired, though. > It appears that I'm still getting link errors even though I've corrected permissions for the pool directories. What else should I be checking? Thanks! -- Kimball |
From: Kimball L. <ki...@mi...> - 2008-02-27 20:23:41
|
Actually, I may have answered my own question somewhat: It appears (based on my reading of a message here: http://www.mail-archive.com/bac...@li.../msg09017.html ) that my pool is hosed. Specifically, my cpool directory has several gigs of data in it, but my "pool" directory is completely empty. Consequently, when it attempts to create the cpool directory, the creation fails as the dir already exists (I'm just guessing here). So, what exactly is the relationship between the cpool and pool directory? How safe is it (I assume NOT safe at all) to remove the contents of cpool? Thanks! -- Kimball On Feb 27, 2008, at 1:11 PM, Les Mikesell wrote: > Kimball Larsen wrote: >>>> I notice that the cpool directory is owned by root. Should it >>>> be owned by the backuppc user instead? >>> Yes, it must be writable by the backuppc user. Your logs are >>> probably full of "unable to link" errors. >>> >> Yeah, I've been getting stuff like this: >> 2008-02-27 11:51:16 BackupPC_link got error -4 when calling >> MakeFileLink( .... >> I've changed the permissions... how soon should I expect to see >> some items wind up in the pool? > > They should be linked during/after each backup run. You won't see > much space benefit from the pooling until your old archives where > the link attempt failed are expired, though. > > -- > Les Mikesell > les...@gm... > |
From: Les M. <le...@fu...> - 2008-02-27 20:30:35
|
Kimball Larsen wrote: > Actually, I may have answered my own question somewhat: > > It appears (based on my reading of a message here: > http://www.mail-archive.com/bac...@li.../msg09017.html > ) that my pool is hosed. > > Specifically, my cpool directory has several gigs of data in it, but > my "pool" directory is completely empty. Consequently, when it > attempts to create the cpool directory, the creation fails as the dir > already exists (I'm just guessing here). > > So, what exactly is the relationship between the cpool and pool > directory? How safe is it (I assume NOT safe at all) to remove the > contents of cpool? Pool is used if you don't have compression enabled, cpool if you do. Whichever is used must be on the same filesystem as the pc directory tree so that hardlinks work between them. If you are getting errors making the links, check that you have space (df) and inodes available (df -i), and that the directory is writable by the backuppc user. -- Les Mikesell les...@gm... |
From: Kimball L. <ki...@mi...> - 2008-02-27 20:36:24
|
On Feb 27, 2008, at 1:33 PM, Les Mikesell wrote: > Kimball Larsen wrote: >> Actually, I may have answered my own question somewhat: >> It appears (based on my reading of a message here: >> http://www.mail-archive.com/bac...@li.../msg09017.html >> ) that my pool is hosed. >> Specifically, my cpool directory has several gigs of data in it, >> but my "pool" directory is completely empty. Consequently, when >> it attempts to create the cpool directory, the creation fails as >> the dir already exists (I'm just guessing here). >> So, what exactly is the relationship between the cpool and pool >> directory? How safe is it (I assume NOT safe at all) to remove >> the contents of cpool? > > Pool is used if you don't have compression enabled, cpool if you do. > Whichever is used must be on the same filesystem as the pc directory > tree so that hardlinks work between them. If you are getting errors > making the links, check that you have space (df) and inodes > available (df -i), and that the directory is writable by the > backuppc user. Hmm....Something is definitely up with my inodes: root@jake:/mnt/plump/backuppc# df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdc2 0 0 0 - / varrun 497169 77 497092 1% /var/run varlock 497169 2 497167 1% /var/lock udev 497169 3232 493937 1% /dev devshm 497169 1 497168 1% /dev/shm lrm 497169 13 497156 1% /lib/modules/ 2.6.22-14-generic/volatile /dev/sda1 0 0 0 - /mnt/tubby /dev/sdb1 0 0 0 - /mnt/portly /dev/sde1 0 0 0 - /mnt/brick /dev/sdd1 0 0 0 - /mnt/plump /dev/sdf10 4294967295 975408 4293991887 1% /media/Hammer USB I notice that all my disks that are ReiserFS do not list any inode info at all... is ReiserFS the problem, then? Should I change the backuppc disk to be ext3? /mnt/plump is a 500GB disk that is dedicated as the backuppc disk. The home dir for backuppc user is /mnt/plump/backuppc, and that is all that is on the disk. Mount shows this: /dev/sdd1 on /mnt/plump type reiserfs (rw,noatime,nodiratime) Further, df -h shows: /dev/sdd1 466G 310G 157G 67% /mnt/plump So, the disk is nowhere near full. Thanks! -- Kimball |
From: Kimball L. <ki...@mi...> - 2008-02-27 21:04:13
|
On Feb 27, 2008, at 1:36 PM, Kimball Larsen wrote: > On Feb 27, 2008, at 1:33 PM, Les Mikesell wrote: > >> Kimball Larsen wrote: >>> Actually, I may have answered my own question somewhat: >>> It appears (based on my reading of a message here: >>> http://www.mail-archive.com/bac...@li.../msg09017.html >>> ) that my pool is hosed. >>> Specifically, my cpool directory has several gigs of data in it, >>> but my "pool" directory is completely empty. Consequently, when >>> it attempts to create the cpool directory, the creation fails as >>> the dir already exists (I'm just guessing here). >>> So, what exactly is the relationship between the cpool and pool >>> directory? How safe is it (I assume NOT safe at all) to remove >>> the contents of cpool? >> >> Pool is used if you don't have compression enabled, cpool if you >> do. Whichever is used must be on the same filesystem as the pc >> directory tree so that hardlinks work between them. If you are >> getting errors making the links, check that you have space (df) and >> inodes available (df -i), and that the directory is writable by the >> backuppc user. > > Hmm....Something is definitely up with my inodes: > > root@jake:/mnt/plump/backuppc# df -i > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/sdc2 0 0 0 - / > varrun 497169 77 497092 1% /var/run > varlock 497169 2 497167 1% /var/lock > udev 497169 3232 493937 1% /dev > devshm 497169 1 497168 1% /dev/shm > lrm 497169 13 497156 1% /lib/modules/ > 2.6.22-14-generic/volatile > /dev/sda1 0 0 0 - /mnt/tubby > /dev/sdb1 0 0 0 - /mnt/portly > /dev/sde1 0 0 0 - /mnt/brick > /dev/sdd1 0 0 0 - /mnt/plump > /dev/sdf10 4294967295 975408 4293991887 1% /media/ > Hammer USB > > I notice that all my disks that are ReiserFS do not list any inode > info at all... is ReiserFS the problem, then? Should I change the > backuppc disk to be ext3? > /mnt/plump is a 500GB disk that is dedicated as the backuppc disk. > The home dir for backuppc user is /mnt/plump/backuppc, and that is > all that is on the disk. Mount shows this: > > /dev/sdd1 on /mnt/plump type reiserfs (rw,noatime,nodiratime) > > Further, df -h shows: > /dev/sdd1 466G 310G 157G 67% /mnt/plump > > So, the disk is nowhere near full. > > Thanks! > > -- Kimball > > So, I poked around in my cpool directory, and found that some of the sub dirs were owned by root - though I have no good explanation as to why. So, I changed ownership recursively to backuppc for the whole cpool directory. Trying to run a backup again still produces a bunch of errors like this: 2008-02-27 13:57:43 BackupPC_link got error -4 when calling MakeFileLink(/mnt/plump/backuppc/pc/192.168.0.8/4/f%2fUsers%2fkathy/ attrib, 9b72d3224906bb9adaa6197f0bfe6f37, 1) So, is this error complaining that it could not write to the pc directory, or to the cpool dir? Should I be looking in the pc directory more carefully? Thanks! -- Kimball |
From: Les M. <le...@fu...> - 2008-02-27 21:45:28
|
Kimball Larsen wrote: > >>> Pool is used if you don't have compression enabled, cpool if you do. >>> Whichever is used must be on the same filesystem as the pc directory >>> tree so that hardlinks work between them. If you are getting errors >>> making the links, check that you have space (df) and inodes available >>> (df -i), and that the directory is writable by the backuppc user. >> >> Hmm....Something is definitely up with my inodes: >> >> root@jake:/mnt/plump/backuppc# df -i >> Filesystem Inodes IUsed IFree IUse% Mounted on >> /dev/sdc2 0 0 0 - / >> varrun 497169 77 497092 1% /var/run >> varlock 497169 2 497167 1% /var/lock >> udev 497169 3232 493937 1% /dev >> devshm 497169 1 497168 1% /dev/shm >> lrm 497169 13 497156 1% >> /lib/modules/2.6.22-14-generic/volatile >> /dev/sda1 0 0 0 - /mnt/tubby >> /dev/sdb1 0 0 0 - /mnt/portly >> /dev/sde1 0 0 0 - /mnt/brick >> /dev/sdd1 0 0 0 - /mnt/plump >> /dev/sdf10 4294967295 975408 4293991887 1% /media/Hammer USB >> >> I notice that all my disks that are ReiserFS do not list any inode >> info at all... is ReiserFS the problem, then? Should I change the >> backuppc disk to be ext3? Reiserfs creates inodes as needed so that's not a problem. Just look at your logs and if you still see 'unable to link' errors, try to find the reason. Trying execute the same ln command as the backuppc user might give you some sort of error message. -- Les Mikesell le...@fu... |
From: Kimball L. <ki...@mi...> - 2008-02-27 22:26:05
|
Ok, I found the problem. Looks like my cpool is in the wrong place, apparently: ln: creating hard link `/var/lib/backuppc/cpool/b/7/6/ b763efe12301fe7645e82fb46d53b4e3' to `/mnt/plump/backuppc/pc/ 192.168.0.8/10/attrib': Invalid cross-device link It looks like my cpool is in /var/lib/backuppc/cpool, but my backups are in /mnt/plump/backuppc. How do I change that? I thought everything was based on the topdir, which I've set to /mnt/plump/backuppc. *confused* -- Kimball On Feb 27, 2008, at 2:48 PM, Les Mikesell wrote: > Kimball Larsen wrote: >>>> Pool is used if you don't have compression enabled, cpool if you >>>> do. Whichever is used must be on the same filesystem as the pc >>>> directory tree so that hardlinks work between them. If you are >>>> getting errors making the links, check that you have space (df) >>>> and inodes available (df -i), and that the directory is writable >>>> by the backuppc user. >>> >>> Hmm....Something is definitely up with my inodes: >>> >>> root@jake:/mnt/plump/backuppc# df -i >>> Filesystem Inodes IUsed IFree IUse% Mounted on >>> /dev/sdc2 0 0 0 - / >>> varrun 497169 77 497092 1% /var/run >>> varlock 497169 2 497167 1% /var/lock >>> udev 497169 3232 493937 1% /dev >>> devshm 497169 1 497168 1% /dev/shm >>> lrm 497169 13 497156 1% /lib/modules/ >>> 2.6.22-14-generic/volatile >>> /dev/sda1 0 0 0 - /mnt/tubby >>> /dev/sdb1 0 0 0 - /mnt/portly >>> /dev/sde1 0 0 0 - /mnt/brick >>> /dev/sdd1 0 0 0 - /mnt/plump >>> /dev/sdf10 4294967295 975408 4293991887 1% /media/ >>> Hammer USB >>> >>> I notice that all my disks that are ReiserFS do not list any inode >>> info at all... is ReiserFS the problem, then? Should I change the >>> backuppc disk to be ext3? > > Reiserfs creates inodes as needed so that's not a problem. Just > look at your logs and if you still see 'unable to link' errors, try > to find the reason. Trying execute the same ln command as the > backuppc user might give you some sort of error message. > > -- > Les Mikesell > le...@fu... > |
From: Les M. <les...@gm...> - 2008-02-27 22:42:28
|
Kimball Larsen wrote: > Ok, I found the problem. Looks like my cpool is in the wrong place, > apparently: > > ln: creating hard link `/var/lib/backuppc/cpool/b/7/6/ > b763efe12301fe7645e82fb46d53b4e3' to `/mnt/plump/backuppc/pc/ > 192.168.0.8/10/attrib': Invalid cross-device link > > It looks like my cpool is in /var/lib/backuppc/cpool, but my backups > are in /mnt/plump/backuppc. > > How do I change that? I thought everything was based on the topdir, > which I've set to /mnt/plump/backuppc. > If you installed from source yourself, everything would be adjusted to where you set topdir during the install. However some of those adjustments involved substituting into the code. If you install a version packaged for a distribution, the topdir is essentially hardcoded to wherever the packager chose. The easy way to use a different location is to copy whatever is under /var/lib/backuppc to your new location and then either mount it at /var/lib/backuppc if it is a separate partition or replace /var/lib/backuppc with a symlink to wherever you want. -- Les Mikesell les...@gm... |
From: Kimball L. <ki...@mi...> - 2008-02-27 22:37:49
|
Ok, I freely admit that I'm in over my head here... I am NOT a perl programmer. However, here is the method that is puking when trying to create the links: sub MakeFileLink { my($bpc, $name, $d, $newFile, $compress) = @_; my($i, $rawFile); return -1 if ( !-f $name ); for ( $i = -1 ; ; $i++ ) { return -2 if ( !defined($rawFile = $bpc->MD52Path($d, $compress)) ); $rawFile .= "_$i" if ( $i >= 0 ); if ( -f $rawFile ) { if ( (stat(_))[3] < $bpc->{Conf}{HardLinkMax} && !compare($name, $rawFile) ) { unlink($name); return -3 if ( !link($rawFile, $name) ); return 1; } } elsif ( $newFile && -f $name && (stat($name))[3] == 1 ) { my($newDir); ($newDir = $rawFile) =~ s{(.*)/.*}{$1}; mkpath($newDir, 0, 0777) if ( !-d $newDir ); return -4 if ( !link($name, $rawFile) ); return 2; } else { return 0; } } } The line: return -4 if ( !link($name, $rawFile) ); is where the problem occurs. How do I get the contents of $name or $rawFile to spit out into the log so I can see for sure where it is trying to link to/from? I'd like to try manually creating the link as Les suggested as the backuppc user, but I'm unsure what to pass to ln in the shell. Here, again, is the error from my log: 2008-02-27 15:03:50 BackupPC_link got error -4 when calling MakeFileLink(/mnt/plump/backuppc/pc/192.168.0.8/6/f%2fUsers%2fkathy/ attrib, 3a473beda0c8d3677d88cd783aa4cc68, 1) I'm just unsure how to take the parameters that are passed to MakeFleLink and convert them into whatever is passed to the link call later. Thanks! -- Kimball On Feb 27, 2008, at 2:48 PM, Les Mikesell wrote: > Kimball Larsen wrote: >>>> Pool is used if you don't have compression enabled, cpool if you >>>> do. Whichever is used must be on the same filesystem as the pc >>>> directory tree so that hardlinks work between them. If you are >>>> getting errors making the links, check that you have space (df) >>>> and inodes available (df -i), and that the directory is writable >>>> by the backuppc user. >>> >>> Hmm....Something is definitely up with my inodes: >>> >>> root@jake:/mnt/plump/backuppc# df -i >>> Filesystem Inodes IUsed IFree IUse% Mounted on >>> /dev/sdc2 0 0 0 - / >>> varrun 497169 77 497092 1% /var/run >>> varlock 497169 2 497167 1% /var/lock >>> udev 497169 3232 493937 1% /dev >>> devshm 497169 1 497168 1% /dev/shm >>> lrm 497169 13 497156 1% /lib/modules/ >>> 2.6.22-14-generic/volatile >>> /dev/sda1 0 0 0 - /mnt/tubby >>> /dev/sdb1 0 0 0 - /mnt/portly >>> /dev/sde1 0 0 0 - /mnt/brick >>> /dev/sdd1 0 0 0 - /mnt/plump >>> /dev/sdf10 4294967295 975408 4293991887 1% /media/ >>> Hammer USB >>> >>> I notice that all my disks that are ReiserFS do not list any inode >>> info at all... is ReiserFS the problem, then? Should I change the >>> backuppc disk to be ext3? > > Reiserfs creates inodes as needed so that's not a problem. Just > look at your logs and if you still see 'unable to link' errors, try > to find the reason. Trying execute the same ln command as the > backuppc user might give you some sort of error message. > > -- > Les Mikesell > le...@fu... > |
From: Kimball L. <ki...@mi...> - 2008-02-27 23:28:49
|
Ok, I finally found and tracked down my problem. I'm using BackupPC on Ubuntu 7.10, which installs BackupPC 3.0.0. Turns out, changing the TopDir location does NOT change the location of the pool files - they are hardcoded to live in /var/lib/backuppc. According to here: http://backuppc.wiki.sourceforge.net/change+archive+directory The solution is as follows: "The archive directory is defined by $TopDir in config.pl. Unfortunately, the current version honors this value for host data, but the pool directories continue to use the default path that is hard- coded at install time. For now, in addition to changing config.pl, you will also need to edit lib/BackupPC/Lib.pm, and change the value in $topDir='/path...'." Changing this file to point to my desired backuppc home dir solved the link problems, and my backups now run error-free. Thanks for all the help! -- Kimball On Feb 27, 2008, at 3:13 PM, Kimball Larsen wrote: > Ok, I freely admit that I'm in over my head here... I am NOT a perl > programmer. However, here is the method that is puking when trying > to create the links: > > sub MakeFileLink > { > my($bpc, $name, $d, $newFile, $compress) = @_; > my($i, $rawFile); > > return -1 if ( !-f $name ); > for ( $i = -1 ; ; $i++ ) { > return -2 if ( !defined($rawFile = $bpc->MD52Path($d, > $compress)) ); > $rawFile .= "_$i" if ( $i >= 0 ); > if ( -f $rawFile ) { > if ( (stat(_))[3] < $bpc->{Conf}{HardLinkMax} > && !compare($name, $rawFile) ) { > unlink($name); > return -3 if ( !link($rawFile, $name) ); > return 1; > } > } elsif ( $newFile && -f $name && (stat($name))[3] == 1 ) { > my($newDir); > ($newDir = $rawFile) =~ s{(.*)/.*}{$1}; > mkpath($newDir, 0, 0777) if ( !-d $newDir ); > return -4 if ( !link($name, $rawFile) ); > return 2; > } else { > return 0; > } > } > } > > > The line: > > return -4 if ( !link($name, $rawFile) ); > > is where the problem occurs. How do I get the contents of $name or > $rawFile to spit out into the log so I can see for sure where it is > trying to link to/from? > > I'd like to try manually creating the link as Les suggested as the > backuppc user, but I'm unsure what to pass to ln in the shell. > > Here, again, is the error from my log: > > 2008-02-27 15:03:50 BackupPC_link got error -4 when calling > MakeFileLink(/mnt/plump/backuppc/pc/192.168.0.8/6/f%2fUsers%2fkathy/ > attrib, 3a473beda0c8d3677d88cd783aa4cc68, 1) > > I'm just unsure how to take the parameters that are passed to > MakeFleLink and convert them into whatever is passed to the link > call later. > > Thanks! > > -- Kimball > > > > On Feb 27, 2008, at 2:48 PM, Les Mikesell wrote: > >> Kimball Larsen wrote: >>>>> Pool is used if you don't have compression enabled, cpool if you >>>>> do. Whichever is used must be on the same filesystem as the pc >>>>> directory tree so that hardlinks work between them. If you are >>>>> getting errors making the links, check that you have space (df) >>>>> and inodes available (df -i), and that the directory is writable >>>>> by the backuppc user. >>>> >>>> Hmm....Something is definitely up with my inodes: >>>> >>>> root@jake:/mnt/plump/backuppc# df -i >>>> Filesystem Inodes IUsed IFree IUse% Mounted on >>>> /dev/sdc2 0 0 0 - / >>>> varrun 497169 77 497092 1% /var/run >>>> varlock 497169 2 497167 1% /var/lock >>>> udev 497169 3232 493937 1% /dev >>>> devshm 497169 1 497168 1% /dev/shm >>>> lrm 497169 13 497156 1% /lib/modules/ >>>> 2.6.22-14-generic/volatile >>>> /dev/sda1 0 0 0 - /mnt/tubby >>>> /dev/sdb1 0 0 0 - /mnt/portly >>>> /dev/sde1 0 0 0 - /mnt/brick >>>> /dev/sdd1 0 0 0 - /mnt/plump >>>> /dev/sdf10 4294967295 975408 4293991887 1% /media/ >>>> Hammer USB >>>> >>>> I notice that all my disks that are ReiserFS do not list any >>>> inode info at all... is ReiserFS the problem, then? Should I >>>> change the backuppc disk to be ext3? >> >> Reiserfs creates inodes as needed so that's not a problem. Just >> look at your logs and if you still see 'unable to link' errors, try >> to find the reason. Trying execute the same ln command as the >> backuppc user might give you some sort of error message. >> >> -- >> Les Mikesell >> le...@fu... >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ |
From: Ludovic D. <ld...@de...> - 2008-02-28 16:28:52
|
Nils Breunese (Lemonbit <nils <at> lemonbit.nl> writes: > The $TopDir relocation after installing a packaged version is > discussed pretty regularly on this list (every week?). The easier > solution is to mount your backup drive/array on the location used by > the packager (/var/lib/backuppc in the case of Ubuntu/Debian) or make > this location a symlink to where you mount your backup drive/array. Yes, you're right ! Shame on people who have never read /usr/share/doc/backuppc/README.Debian ! "If you do not like the default data directory (/var/lib/backuppc/), you should move this directory where you want and make a symbolic link from the new directory to the default one (all paths are hardcoded so it's the easiest way to change the data directory)." Cheers, Ludovic. |
From: Tomasz C. <ma...@wp...> - 2008-02-27 20:08:45
|
Kimball Larsen schrieb: > On Feb 27, 2008, at 11:49 AM, Les Mikesell wrote: >> Kimball Larsen wrote: >>> I've recently had to move my backuppc filesystem from one machine >>> to another. My machines are all backing up just fine, I'm able to >>> see all my old backups and restore files from them with no >>> problem.. however, my pool size is reporting as 0MB. I checked >>> the filesystem, and the size of the pool directory is in fact 0. >>> Here is some info from the shell: >>> root@jake:/mnt/plump/backuppc# du -sh pool >>> 0 pool >>> root@jake:/mnt/plump/backuppc# ls -la >>> total 4 >>> drwxr-x--- 9 backuppc backuppc 240 2008-02-27 10:37 . >>> drwxr-xr-x 5 root root 104 2008-02-19 12:55 .. >>> drwxr-x--- 12 root root 288 2008-02-19 11:27 cpool >>> drwxr-x--- 2 backuppc root 128 2007-07-28 03:00 log >>> drwx------ 2 backuppc root 48 2007-07-27 16:10 Mail >>> drwxr-x--- 9 backuppc root 272 2008-02-26 15:26 pc >>> drwxr-x--- 2 backuppc root 48 2007-05-20 15:14 pool >>> -rw------- 1 backuppc root 812 2007-07-27 16:19 sent >>> drwx------ 2 backuppc root 200 2008-02-20 07:37 .ssh >>> drwxr-x--- 2 backuppc backuppc 48 2008-02-27 10:50 trash >>> root@jake:/mnt/plump/backuppc# du -sh cpool >>> 1.6G cpool >>> I notice that the cpool directory is owned by root. Should it be >>> owned by the backuppc user instead? >> Yes, it must be writable by the backuppc user. Your logs are >> probably full of "unable to link" errors. >> > > Yeah, I've been getting stuff like this: > 2008-02-27 11:51:16 BackupPC_link got error -4 when calling > MakeFileLink( .... > > I've changed the permissions... how soon should I expect to see some > items wind up in the pool? If you have compression enabled in your configuration, you won't see any items in "pool" directory, but in "cpool" one (compressed pool). I would also restart backuppc after correcting the permissions. -- Tomasz Chmielewski http://wpkg.org |
From: Nils B. (Lemonbit) <ni...@le...> - 2008-02-27 23:37:46
|
Kimball Larsen wrote: > Ok, I finally found and tracked down my problem. > > I'm using BackupPC on Ubuntu 7.10, which installs BackupPC 3.0.0. > Turns out, changing the TopDir location does NOT change the location > of the pool files - they are hardcoded to live in /var/lib/backuppc. > > According to here: > http://backuppc.wiki.sourceforge.net/change+archive+directory > The solution is as follows: > > "The archive directory is defined by $TopDir in config.pl. > Unfortunately, the current version honors this value for host data, > but the pool directories continue to use the default path that is > hard-coded at install time. For now, in addition to changing > config.pl, you will also need to edit lib/BackupPC/Lib.pm, and > change the value in $topDir='/path...'." > > Changing this file to point to my desired backuppc home dir solved > the link problems, and my backups now run error-free. > > Thanks for all the help! The $TopDir relocation after installing a packaged version is discussed pretty regularly on this list (every week?). The easier solution is to mount your backup drive/array on the location used by the packager (/var/lib/backuppc in the case of Ubuntu/Debian) or make this location a symlink to where you mount your backup drive/array. But yeah, chaning the files will also work. But you'll have to edit those files again when you install an upgrade, so I recommend just mounting your backup drive on /var/lib/backuppc (you can also use a bind mount) or using a symlink. Nils Breunese. |
From: dan <dan...@gm...> - 2008-02-28 02:02:24
|
the $TopDIR must be on the same volume as the backup files. so if $TopDIR is /var/lib/backuppc and /var is a 500GB drive then your pc directory needs to be somewhere in /var. What I do and what is common to do is to mount up the target drive somewhere temporarily and `cp -Rp /var/lib/backuppc /target/drive` then remount that drive to /var/lib/backuppc. then make sure that $TopDIR is /var/lib/backuppc. as i understand it, this is just an ubunty/debian issue as the deb files are compiled to hardcode $TopDIR. if you install from source you can put $TopDIR anywhere you like BUT you still have to put the backup files on the same filesystem for hardlinks to work. On Wed, Feb 27, 2008 at 4:37 PM, Nils Breunese (Lemonbit) <ni...@le...> wrote: > Kimball Larsen wrote: > > > Ok, I finally found and tracked down my problem. > > > > I'm using BackupPC on Ubuntu 7.10, which installs BackupPC 3.0.0. > > Turns out, changing the TopDir location does NOT change the location > > of the pool files - they are hardcoded to live in /var/lib/backuppc. > > > > According to here: > > http://backuppc.wiki.sourceforge.net/change+archive+directory > > The solution is as follows: > > > > "The archive directory is defined by $TopDir in config.pl. > > Unfortunately, the current version honors this value for host data, > > but the pool directories continue to use the default path that is > > hard-coded at install time. For now, in addition to changing > > config.pl, you will also need to edit lib/BackupPC/Lib.pm, and > > change the value in $topDir='/path...'." > > > > Changing this file to point to my desired backuppc home dir solved > > the link problems, and my backups now run error-free. > > > > Thanks for all the help! > > The $TopDir relocation after installing a packaged version is > discussed pretty regularly on this list (every week?). The easier > solution is to mount your backup drive/array on the location used by > the packager (/var/lib/backuppc in the case of Ubuntu/Debian) or make > this location a symlink to where you mount your backup drive/array. > > But yeah, chaning the files will also work. But you'll have to edit > those files again when you install an upgrade, so I recommend just > mounting your backup drive on /var/lib/backuppc (you can also use a > bind mount) or using a symlink. > > Nils Breunese. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |