Project

General

Profile

« Previous | Next » 

Revision 13022

Added by Aaron Marcuse-Kubitza over 10 years ago

fix: /README.TXT: Full database import: disk space: increased the minimum free space recommendation to 1 TB, because analysis of the disk usage during the beginning of the import shows that actually close to the entire amount is being used. however, this problem is normally undetectable unless the disk space is specifically checked, because it only manifests itself if the available disk space is exceeded completely.

View differences:

trunk/README.TXT
64 64 
	restart Postgres to free up any disk space used by temp tables from the last
65 65 
		import (this is apparently not automatically reclaimed):
66 66 
		make postgres_restart
67 
	Make sure there is at least 500GB of disk space on /: df -h
68 
		The import schema is 315GB, and may use significant additional space for
69 
			temp tables
67 
	Make sure there is at least 1 TB of disk space on /: df -h
68 
		**WARNING**: sometimes, this amount of available space is insufficient
69 
			and the entire disk space gets used up, crashing the import. if this
70 
			occurs, the problem will often be fixed just by rerunning the import
71 
			again. (the high-water mark varies by import.)
72 
		although the import schema itself is only 315 GB, Postgres uses
73 
			significant temporary space at the beginning of the import. the
74 
			total disk usage reaches 1.7+ TB in the first hour
75 
			("14:00:25"-"12:55:09"), and then oscillates between 1.2-1.6 TB in
76 
			the following 2+ hours.
70 77 
		To free up space, remove backups that have been archived on jupiter:
71 78 
			List backups/ to view older backups
72 79 
			Check their MD5 sums using the steps under On jupiter below

Also available in: Unified diff