We've learned that GBase Database installation failures, often showing a «No space left on device» error, frequently stem from insufficient space in the /tmp temporary file directory, not the main disk. This means you might need to check your /tmp space or direct the installer to use an alternative temporary directory.
Ever encountered a «No space left on device» error while installing a GBase 8s database, even when you know your main disk has tons of room? It's a common, frustrating issue, and the real culprit isn't what you might think! What this means for you is that the problem likely isn't your main storage, but rather your system's temporary file directory, /tmp.
The installer suddenly quits, giving you error messages suggesting the disk is full. Naturally, you'd check your main installation directory, like /opt, only to find dozens of gigabytes readily available. It's incredibly confusing.
The core issue is that the GBase installer often uses the /tmp directory to extract temporary files and installation components. If this space is insufficient, the installation will fail, regardless of your main disk's capacity. And it's not just about raw space; sometimes a filesystem can run out of 'inodes', which are like pointers to files, leading to the same «No space left» error even when `df -h` still shows available capacity.
To avoid this, your first step should always be to check the /tmp filesystem's space using commands like `df -h /tmp` for disk space and `df -i /tmp` for inode usage. You can also look for large files in /tmp that might be leftovers from previous installations.
If /tmp is indeed full, you can try safely removing old temporary files. However, a cleaner and more robust solution is to tell the GBase installer to use a dedicated temporary directory. You can create a new directory, for example, `/opt/tmp`, then set the `TMPDIR` environment variable to point to this new location before starting the installation. This approach helps you bypass potential issues with the default /tmp and gives you better control over the temporary storage needed for your installation.
The installer suddenly quits, giving you error messages suggesting the disk is full. Naturally, you'd check your main installation directory, like /opt, only to find dozens of gigabytes readily available. It's incredibly confusing.
The core issue is that the GBase installer often uses the /tmp directory to extract temporary files and installation components. If this space is insufficient, the installation will fail, regardless of your main disk's capacity. And it's not just about raw space; sometimes a filesystem can run out of 'inodes', which are like pointers to files, leading to the same «No space left» error even when `df -h` still shows available capacity.
To avoid this, your first step should always be to check the /tmp filesystem's space using commands like `df -h /tmp` for disk space and `df -i /tmp` for inode usage. You can also look for large files in /tmp that might be leftovers from previous installations.
If /tmp is indeed full, you can try safely removing old temporary files. However, a cleaner and more robust solution is to tell the GBase installer to use a dedicated temporary directory. You can create a new directory, for example, `/opt/tmp`, then set the `TMPDIR` environment variable to point to this new location before starting the installation. This approach helps you bypass potential issues with the default /tmp and gives you better control over the temporary storage needed for your installation.
