This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

Disk space required for importing planet.osm into PostgreSQL w/ Osmosis?

I've been trying to import this beast into PostgreSQL. I've been using EC2 since I don't have enough HDD space myself.

My last attempt on a large EC2 instance, with 850GB, failed because it ran out of disk space. I have a graph to show it hitting the 850GB:

Graph showing disk space running out

I'd like to know approximately how much space I need, or maybe 850GB is way bigger than required and Osmosis is going into an infinite loop?

I couldn't find out how to enable logging on osmosis, so I can see how far it's gone into the import.

The command I'm using is:

time bzcat planet-latest.osm.bz2 | osmosis --read-xml file="/dev/stdin" enableDateParsing=no --write-pgsql user="osm" database="osm" password="osm"

For my next attempt I'll give it 1TB.. I'll update this question appropriately with my results.

postgresql osmosis

asked 14 Feb '11, 00:59

gak
36●1●1●6
accept rate: 0%

edited 14 Feb '11, 03:13

Update: I had a strange parsing error with Osmosis, so this test is on hold for now. I'm testing my development with australia.osm for now (which was ~3.4GB). I'll update this if I ever get planet.osm going.

(15 Feb '11, 04:55) gak

One Answer:

1	I think there is something wrong. yevaud, the mapnik-rendering-Server, has this configuration: `/database - sdb - 4x 300GB 10kRPM (RAID10)` the usage is at 60% answered 16 Feb '11, 14:32 josias 598●7●15●23 accept rate: 33% Thanks, I'll look into the problem. (16 Feb '11, 21:22) gak