Author: Rob Owens <rob.owens AT biochemfluidics DOT com>
Date: Mon, 08 Sep 2008 12:06:46 -0400
I rebooted my BackupPC server after a RAM upgrade, and warned me of errors on my /var/lib/backuppc partition. So I ran e2fsck -p -v on the partition, and I get a whole lot of: /dev/md5: Problem in HT
Author: Les Mikesell <les AT futuresource DOT com>
Date: Mon, 08 Sep 2008 12:24:17 -0500
If you have to ask advice, you probably need to say yes here. And if there are hundreds of errors you might as well run fsck with the -y option. fsck knows more than most of us about how to recover a
Author: Rob Owens <rob.owens AT biochemfluidics DOT com>
Date: Mon, 08 Sep 2008 13:31:06 -0400
Agreed. I'm giving it a shot. My concern was that if a file got corrupted, would BackupPC notice or would it allow new files to be hardlinked to the corrupted files in the pool. I guess a full backup
Author: Les Mikesell <les AT futuresource DOT com>
Date: Mon, 08 Sep 2008 12:40:38 -0500
I think the hashed filename in the pool is just a quick initial check for possible matches and there is a full data comparison before new files would be replaced with links. -- Les Mikesell lesmikese
Author: Holger Parplies <wbppc AT parplies DOT de>
Date: Mon, 8 Sep 2008 21:18:36 +0200
Hi, Les Mikesell wrote on 2008-09-08 12:40:38 -0500 [Re: [BackupPC-users] fsck of /var/lib/backuppc]: I can confirm that. It's not actually "replaced" for existing files in the pool. If candidates ex