[SOLVED] "write error (disk full?)" after pack 4 update

[wilberfan]

I'm running LMDE-XFCE and performed the pack 4 update 2 nights ago.

I have a chromium-update script that worked fine before the dist-upgrade, but now fails during an unzip step.

Here's the script:

Code: Select all

#!/bin/bash
echo "*** Update script for Chromium nightly builds ***"
echo "*** Written by: loganfynne ***"
mkdir /tmp/chromium-nightly
cd /tmp/chromium-nightly
wget http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux/L$
NEW="`cat LAST_CHANGE`"
wget http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux/$$
# chmod 777 chrome-linux.zip
unzip -q -o -d /tmp/chromium-nightly/ chrome-linux.zip
rm -r /usr/lib/chromium
mkdir /usr/lib/chromium
mv /tmp/chromium-nightly/chrome-linux/* /usr/lib/chromium/
chmod 644 /usr/lib/chromium/*
chmod 755 /usr/lib/chromium/locales
chmod 644 /usr/lib/chromium/locales/*
chmod +x /usr/lib/chromium/chrome
rm -r /tmp/chromium-nightly/*

Here are the results of running the script:

Code: Select all

$ sudo chromium-update
[sudo] password for wilberfan: 
*** Update script for Chromium nightly builds ***
*** Written by: loganfynne ***
--2012-04-10 20:05:28--  http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux/LAST_CHANGE
Resolving commondatastorage.googleapis.com (commondatastorage.googleapis.com)... 74.125.224.203, 74.125.224.204, 74.125.224.202
Connecting to commondatastorage.googleapis.com (commondatastorage.googleapis.com)|74.125.224.203|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6 [text/plain]
Saving to: `LAST_CHANGE'

100%[======================================>] 6           --.-K/s   in 0s      

2012-04-10 20:05:29 (348 KB/s) - `LAST_CHANGE' saved [6/6]

--2012-04-10 20:05:29--  http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip
Resolving commondatastorage.googleapis.com (commondatastorage.googleapis.com)... 74.125.224.202, 74.125.224.204, 74.125.224.203
Connecting to commondatastorage.googleapis.com (commondatastorage.googleapis.com)|74.125.224.202|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://v9.lscache1.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip [following]
--2012-04-10 20:05:30--  http://v9.lscache1.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip
Resolving v9.lscache1.c.bigcache.googleapis.com (v9.lscache1.c.bigcache.googleapis.com)... 8.21.196.15
Connecting to v9.lscache1.c.bigcache.googleapis.com (v9.lscache1.c.bigcache.googleapis.com)|8.21.196.15|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://v9.nonxt1.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip?redirect_counter=1 [following]
--2012-04-10 20:05:30--  http://v9.nonxt1.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip?redirect_counter=1
Resolving v9.nonxt1.c.bigcache.googleapis.com (v9.nonxt1.c.bigcache.googleapis.com)... 173.194.7.147
Connecting to v9.nonxt1.c.bigcache.googleapis.com (v9.nonxt1.c.bigcache.googleapis.com)|173.194.7.147|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://v1.cache2.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip?redirect_counter=2 [following]
--2012-04-10 20:05:30--  http://v1.cache2.c.bigcache.googleapis.com/chromium-browser-snapshots/Linux/131703/chrome-linux.zip?redirect_counter=2
Resolving v1.cache2.c.bigcache.googleapis.com (v1.cache2.c.bigcache.googleapis.com)... 74.125.213.48
Connecting to v1.cache2.c.bigcache.googleapis.com (v1.cache2.c.bigcache.googleapis.com)|74.125.213.48|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 43844590 (42M) [application/zip]
Saving to: `chrome-linux.zip'

100%[======================================>] 43,844,590  2.54M/s   in 15s     

2012-04-10 20:05:46 (2.71 MB/s) - `chrome-linux.zip' saved [43844590/43844590]

/tmp/chromium-nightly/chrome-linux/chrome:  write error (disk full?).  Continue? (y/n/^C) n

warning:  /tmp/chromium-nightly/chrome-linux/chrome is probably truncated

There's plenty of room available, so I'm not sure what the problem is...

$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 11G 5.0G 4.8G 52% /
udev 247M 0 247M 0% /dev
/dev/disk/by-uuid/455f0c13-e7dd-45b5-aa29-c328441cdd12 11G 5.0G 4.8G 52% /
tmpfs 51M 764K 50M 2% /var/run
tmpfs 5.0M 4.0K 5.0M 1% /var/run/lock
tmpfs 101M 36K 101M 1% /tmp
tmpfs 101M 92K 101M 1% /var/run/shm

[doktornotor]

/tmp/chromium-nightly/chrome-linux/chrome: write error (disk full?). Continue? (y/n/^C) n

There's plenty of room available, so I'm not sure what the problem is...

$ sudo df -h
tmpfs 101M 36K 101M 1% /tmp

Plenty? Really? Do not use /tmp on tmpfs if all you have is measly 512MiB of RAM. See /etc/default/rcS

[wilberfan]

/tmp/chromium-nightly/chrome-linux/chrome: write error (disk full?). Continue? (y/n/^C) n

There's plenty of room available, so I'm not sure what the problem is...

$ sudo df -h
tmpfs 101M 36K 101M 1% /tmp

Plenty? Really? Do not use /tmp on tmpfs if all you have is measly 512MiB of RAM. See /etc/default/rcS

Well, you're awesome, and I'm definitely a noob. I had no idea about the RAMTMP=yes/no option in /etc/default/rcS. I'd been checking properties on the /tmp file via thunar and it showed plenty of available space. (And, obviously, didn't look close enough at the df -h output.

I changed RAMTMP= to no, rebooted, and my script ran excellente! Many thanks!

[pokemon321]

Hi, I had the same error, you can also use 7z to unzip the file.

7z e 'zipfile'