Question: could not extend file "base/361191441/368615606.137": No space left on device #2093
-
On an HDD-based Ubuntu system, I fully imported the planet file monthly. However, the last import failed due to lack of disk space.
Questions:
Additional question:
Import command:
osm2pgsql output:
HDD space:
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
PostgreSQL
Buy a bigger hard disk. Or run without
https://osm2pgsql.org/doc/faq.html#can-osm2pgsql-resume-after-a-failed-import |
Beta Was this translation helpful? Give feedback.
-
Update 1: The server used has 128728.9 MiB of RAM. The import without the options '--slim, --drop, --cache' was not successful. All the free disk space was used up by the (parallel) indexing operations:
However, omitting the '--slim, --drop, --cache' options significantly sped up the 'pure' import of raw data (6h 25m 8s versus 55h 47m 4s): With '--slim, --drop, --cache':
Without '--slim, --drop, --cache':
Import command:
Next step:
|
Beta Was this translation helpful? Give feedback.
-
You should move your database to the bigger disk at /dev/md3. Either use tablespaces or move the entire PostgreSQL cluster over. |
Beta Was this translation helpful? Give feedback.
-
Even with the option '--disable-parallel-indexing' the import of the planet file was not successful. 705 GB of free disk space is not enough for this.
Next step:
|
Beta Was this translation helpful? Give feedback.
-
I have moved the database data directory to a bigger partion. This is what I have done (maybe helpful for others): Preparation (identification of required information):
Migration (running 5 hours):
(Helpful) Links concerning migration: Old situation:
New situation:
After migration I was able to import the planet file:
The new import command without the options '--slim, --drop, --cache and --flat-nodes' is much faster (over 42 hours): And this is my final import command:
BTW: The database is continuously growing by over 40 GB per year (database size after osm2pgsql step and before any additional indexing):
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the support. |
Beta Was this translation helpful? Give feedback.
You should move your database to the bigger disk at /dev/md3. Either use tablespaces or move the entire PostgreSQL cluster over.