When running an executable file (such as a patch for a game), I get an error message saying that the installer couldn't start, and that I may be out of disk space. I'm fairly certain this is untrue. I'm pretty new to Linux.
Anybody able to help?
Disk space error
Disk space error
On Wed, 2011-06-08 at 14:01 -0500, thrdwrld wrote:
If the patch executable size is more than 20-25% of the free space you
might be short of disk space. Otherwise the problem may be elsewhere.
Most distros have three or fewer partitions by default: /root, swap,
and /, which contains the entire filing system. If you have more
partitions than that ans can't figure out which may be running out of
space, post the output from df here and tell us where you are running
from ('echo $HOME') and where you've put Wine's virtual filing system
('echo $WINEPREFIX', 'ls -l $WINEPREFIX').
Martin
Run 'df' in terminal to see how much space there is free on your disk.When running an executable file (such as a patch for a game), I get an
error message saying that the installer couldn't start, and that I may
be out of disk space. I'm fairly certain this is untrue. I'm pretty
new to Linux.
If the patch executable size is more than 20-25% of the free space you
might be short of disk space. Otherwise the problem may be elsewhere.
Most distros have three or fewer partitions by default: /root, swap,
and /, which contains the entire filing system. If you have more
partitions than that ans can't figure out which may be running out of
space, post the output from df here and tell us where you are running
from ('echo $HOME') and where you've put Wine's virtual filing system
('echo $WINEPREFIX', 'ls -l $WINEPREFIX').
Martin
k-ub@K-Ub:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 192245340 21119024 161360736 12% /
none 1972492 748 1971744 1% /dev
none 1980196 152 1980044 1% /dev/shm
none 1980196 216 1979980 1% /var/run
none 1980196 0 1980196 0% /var/lock
I'm running from sda5. Also noteworthy: i have windows on the same machine in a different partition.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 192245340 21119024 161360736 12% /
none 1972492 748 1971744 1% /dev
none 1980196 152 1980044 1% /dev/shm
none 1980196 216 1979980 1% /var/run
none 1980196 0 1980196 0% /var/lock
I'm running from sda5. Also noteworthy: i have windows on the same machine in a different partition.
Disk space error
On Wed, 2011-06-08 at 15:05 -0500, thrdwrld wrote:
Unless your patch is basically a 54GB self-extracting zip archive or
works by downloading 163 GB over the net, which would take a few days, I
don't think you're going to run out of disk space, so that's very
unlikely to be the problem.
FYI, if you have problems converting a number of 1K blocks into actual
disk space, run 'df -h' rather than 'df'. Here's the difference:
[kiwi@zappa ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 2016488 471016 1443036 25% /
tmpfs 508372 836 507536 1% /dev/shm
/dev/sda1 505132 66710 412342 14% /boot
/dev/sda8 86639024 7810108 74427864 10% /home
/dev/sda5 2016488 39516 1874536 3% /tmp
/dev/sda2 20158372 6167940 12966432 33% /usr
/dev/sda6 2016488 486704 1427348 26% /var
[kiwi@zappa ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 2.0G 460M 1.4G 25% /
tmpfs 497M 836K 496M 1% /dev/shm
/dev/sda1 494M 66M 403M 14% /boot
/dev/sda8 83G 7.5G 71G 10% /home
/dev/sda5 2.0G 39M 1.8G 3% /tmp
/dev/sda2 20G 5.9G 13G 33% /usr
/dev/sda6 2.0G 476M 1.4G 26% /var
[kiwi@zappa ~]$
Martin
But you have 163 GB free on /dev/sda5.k-ub@K-Ub:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 192245340 21119024 161360736 12% /
none 1972492 748 1971744 1% /dev
none 1980196 152 1980044 1% /dev/shm
none 1980196 216 1979980 1% /var/run
none 1980196 0 1980196 0% /var/lock
I'm running from sda5. Also noteworthy: i have windows on the same
machine in a different partition.
Unless your patch is basically a 54GB self-extracting zip archive or
works by downloading 163 GB over the net, which would take a few days, I
don't think you're going to run out of disk space, so that's very
unlikely to be the problem.
FYI, if you have problems converting a number of 1K blocks into actual
disk space, run 'df -h' rather than 'df'. Here's the difference:
[kiwi@zappa ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 2016488 471016 1443036 25% /
tmpfs 508372 836 507536 1% /dev/shm
/dev/sda1 505132 66710 412342 14% /boot
/dev/sda8 86639024 7810108 74427864 10% /home
/dev/sda5 2016488 39516 1874536 3% /tmp
/dev/sda2 20158372 6167940 12966432 33% /usr
/dev/sda6 2016488 486704 1427348 26% /var
[kiwi@zappa ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 2.0G 460M 1.4G 25% /
tmpfs 497M 836K 496M 1% /dev/shm
/dev/sda1 494M 66M 403M 14% /boot
/dev/sda8 83G 7.5G 71G 10% /home
/dev/sda5 2.0G 39M 1.8G 3% /tmp
/dev/sda2 20G 5.9G 13G 33% /usr
/dev/sda6 2.0G 476M 1.4G 26% /var
[kiwi@zappa ~]$
Martin
Disk space error
On Wed, Jun 8, 2011 at 5:22 PM, thrdwrld <[email protected]> wrote:
post the log at pastebin.com and link here.
http://wiki.winehq.org/FAQ#get_log
John
Start your program from the terminal and get the log if it is largeAny idea what could be wrong? (since it obviously isn't disk space)
post the log at pastebin.com and link here.
http://wiki.winehq.org/FAQ#get_log
John
-
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
Disk space error
On 6/8/11 1:51 PM, Martin Gregorie wrote:
large numbers. Sadly, the solution is to either fill up the partition
until the patch runs or to create a temporary partition with a small
enough area to allow the patch to run.
This may be a problem with older programs that cannot work with suchOn Wed, 2011-06-08 at 15:05 -0500, thrdwrld wrote:But you have 163 GB free on /dev/sda5.k-ub@K-Ub:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 192245340 21119024 161360736 12% /
none 1972492 748 1971744 1% /dev
none 1980196 152 1980044 1% /dev/shm
none 1980196 216 1979980 1% /var/run
none 1980196 0 1980196 0% /var/lock
I'm running from sda5. Also noteworthy: i have windows on the same
machine in a different partition.
large numbers. Sadly, the solution is to either fill up the partition
until the patch runs or to create a temporary partition with a small
enough area to allow the patch to run.