id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
915	the timers used by tahoe backup to trigger repair for unhealthy files should be configurable	davidsarah		"Reported by Kyle Markley:
> I am nervous about synchronization between backupdb.sqlite and the  grid.  As happened recently, if a large chunk of the grid goes down, some files may go below their minimum number of shares.  I could repair those files by re-uploading them, but the backupdb assumes those files are fine.  So those files won't be reuploaded and they'll stay broken on the grid -- possibly forever.  I'll think they're backed up, but they aren't!  I'd like to have some way for a deep-check to inject a dose of reality into my backupdb.

> For extra credit, I'd like behavior that's a hybrid between backup and deep-check.  Run a backup operation, but check every file as we go along, and repair or re-upload the file if the grid doesn't have enough shares.

(Actually it should be if there are insufficient servers of happiness for the file, as per #614.)"	defect	new	major	eventually	code-frontend-cli	1.5.0		tahoe-backup preservation usability