Page 1 of 1
[SOLVED] usm "No space left on device" with 120MB free?
Posted: 21 Dec 2015, 22:10
by datruche
Hi!
changes.dat has become too small to update all the slack's pkg dbs. So till I
can enlarge the former while preserving the customization , I've moved /tmp/usm to the hard drive and symlinked it to /tmp/usm. That HDD partition sda7 has lots of free room.
$ df -hT (just after the update could not finish)
Code: Select all
Sys. de fichiers Type Taille Utilisé Dispo Uti% Monté sur
aufs aufs 509M 389M 120M 77% /
devtmpfs devtmpfs 500M 0 500M 0% /dev
/dev/sda7 ext4 62G 22G 37G 38% /mnt/sda7
/dev/sdb1 vfat 7,3G 4,1G 3,2G 57% /mnt/sdb1
/mnt/live/run none 500M 11M 490M 3% /run
# usm -u all
Code: Select all
<SNIP SNIP>
Starting slackonly database update
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz DONE
File verification was good.
bunzip2: I/O or other error, bailing out. Possible reason follows.
bunzip2: No space left on device
Input file = /var/usm/slackonly/MANIFEST.bz2, output file = /var/usm/slackonly/MANIFEST
bunzip2: Deleting output file /var/usm/slackonly/MANIFEST, if it exists.
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
usm update_database 289
Could not decompress: MANIFEST.bz2
==============================================================================
That is anytime I've tried.
How to update usm here?
As this box has got 1 gig I'm thinking it may be a tmpfs issue, if usm uses RAM for decompression.
Re: usm "No space left on device" when there's quite some?
Posted: 21 Dec 2015, 22:13
by brokenman
/tmp/usm to the hard drive and symlinked it to /tmp/usm
So that takes care of the packages that you download. The database files are stored in /var/usm. Please take a look at the config file in /etc/usm.conf and change the path there.
Re: usm "No space left on device" when there's quite some?
Posted: 21 Dec 2015, 22:19
by datruche
Thanks brokenmann
I considered that, and thought slackonly's db wouldn't needs over the 120 MB that are available on the device. Does it?
# du --max-depth=1 -m /var/usm/
Code: Select all
1 /var/usm/local
1 /var/usm/alien
1 /var/usm/salix
1 /var/usm/slacky
1 /var/usm/ponce
2 /var/usm/slackware
1 /var/usm/slackwarepatches
18 /var/usm/slackonly
22 /var/usm/
EDIT: Yes it does (answering myself)
Code: Select all
Starting slackonly database update
Downloading: vercheck.txt DONE
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz DONE
File verification was good.
Optimizing manifest
slackonly database updated.
Starting sbo database update
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz DONE
sbo database updated.
Wooow that makes a 512 MB changes.dat really too small for any serious customization -> lesson learnt.
Re: [SOLVED] usm "No space left on device" with 120MB free?
Posted: 21 Dec 2015, 22:48
by Ed_P
USM for me is only 16MB and I just updated it.
Code: Select all
guest@porteus:~$ ./savedatspaceused.sh
Enter root's password
Password:
du -sh
219M /mnt/live/memory/images/changes
df -h
Filesystem Size Used Avail Use% Mounted on
- 316M 236M 80M 75% /mnt/live/memory/images/changes
344K /mnt/live/memory/images/changes/etc
181M /mnt/live/memory/images/changes/home
32K /mnt/live/memory/images/changes/root
3.6M /mnt/live/memory/images/changes/usr
34M /mnt/live/memory/images/changes/var
48M /mnt/live/memory/images/changes/home/guest/.wine
Press Enter for more details, Ctrl+C to end.
96K /mnt/live/memory/images/changes/etc/usm
ls /mnt/live/memory/images/changes/etc/usm
extra-deps.txt mirrors-salix.txt mirrors-slacky.txt
files.conf mirrors-sbo.txt suppliment-libs.txt
ignore-deps.txt mirrors-slackonly.txt suppliment-optifest.txt
mirrors-alien.txt mirrors-slackware.txt usm.conf
mirrors-ponce.txt mirrors-slackwarepatches.txt version.txt
2.1M /mnt/live/memory/images/changes/var/log
16M /mnt/live/memory/images/changes/var/usm
464K /mnt/live/memory/images/changes/var/usm/alien
200K /mnt/live/memory/images/changes/var/usm/local
640K /mnt/live/memory/images/changes/var/usm/ponce
704K /mnt/live/memory/images/changes/var/usm/salix
2.8M /mnt/live/memory/images/changes/var/usm/sbo
9.1M /mnt/live/memory/images/changes/var/usm/slackonly
1.4M /mnt/live/memory/images/changes/var/usm/slackware
184K /mnt/live/memory/images/changes/var/usm/slackwarepatches
580K /mnt/live/memory/images/changes/var/usm/slacky
As for modules I download with USM I store them outside of Porteus on a NTFS partition which I reference with a extramod= cheatcode. No symlink needed.
Code: Select all
changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules
And as for the size of my Modules folder, well that's another story.
Code: Select all
guest@porteus:~$ ls -l /mnt/sda5/porteus3.1/Modules
total 697672
-rwxrwxrwx 1 root root 4096 Jan 24 2015 001-core_alldesktops-150124.xzm*
-rwxrwxrwx 1 root root 12288 Jan 26 2015 002-xorg_alldesktops-150126.xzm*
-rwxrwxrwx 1 root root 4096 Jan 20 2015 004-lxqt_fixes-150120.xzm*
-rwxrwxrwx 1 root root 71360512 Dec 12 2014 07-printing.xzm*
-rwxrwxrwx 1 root root 3346432 Dec 6 01:18 KeePass-2.30-x86_64-2_slack.xzm*
-rwxrwxrwx 1 root root 184147968 Sep 25 2014 MyWines.xzm*
-rwxrwxrwx 1 root root 299610112 Sep 19 2014 Wine-1.7.26-x64-GeckoMono-1.xzm*
-rwxrwxrwx 1 root root 3252224 Dec 10 20:12 database-usm-20151210.xzm*
-rwxrwxrwx 1 root root 5496832 Dec 10 20:12 flashplayer-plugin-11.2.202.554-x86_64-1alien.xzm*
-rwxrwxrwx 1 root root 12288 Jun 3 2015 java-builder-1.1_noarch.xzm*
-rwxrwxrwx 1 root root 55930880 Dec 10 23:04 jre-8u66-x86_64-1.xzm*
-rwxrwxrwx 1 root root 778240 Dec 6 01:17 keepassx-0.4.3-x86_64-2_slack.xzm*
drwxrwxrwx 1 root root 0 Dec 20 2014 kpat/
-rwxrwxrwx 1 root root 44175360 Nov 14 01:49 mozilla-firefox-38.4.0esr-x86_64-1_slack14.1.xzm*
-rwxrwxrwx 2 root root 40120320 Jul 13 23:04 upkernel-3.18.18-noarch-1.xzm*
-rwxrwxrwx 1 root root 110592 Dec 21 2014 xgames-0.3-x86_64-4.xzm*
-rwxrwxrwx 1 root root 6053888 Jan 21 2015 xscreensaver-5.29-x86_64-1_slack14.1.xzm*
Re: [SOLVED] usm "No space left on device" with 120MB free?
Posted: 21 Dec 2015, 23:11
by datruche
@Ed_P
1. yeah thus my syrprise with 120 MB free left in / (aufs)
2.
Code: Select all
changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules
Aha, much more portable too
Now what about the /tmp/{usm,usmbo,*), that can't be extramod'ed, can it?
3. yeap, not surprising if Porteus's your main or dayly distro of choice.
Thanks for the sharing!
Re: [SOLVED] usm "No space left on device" with 120MB free?
Posted: 22 Dec 2015, 00:08
by Ed_P
datruche wrote:2.
Code: Select all
changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules
Aha, much more portable too
Now what about the /tmp/{usm,usmbo,*), that can't be extramod'ed, can it?
With the changes=EXIT cheatcode the /tmp folder is not saved. Along with several others. The main thing I like with the EXIT option is if I screw up some things testing I can bypass updating the save.dat file when rebooting.
3. yeap, not surprising if Porteus's your main or dayly distro of choice.
Actually I would say my main distro is Windows but my Porteus distro is a very functioning system for the apps that I like. One still missing and maybe I don't really need it.
When my main system was down for a week or so I used Porteus exclusively and didn't miss a beat imo.
I have x86 versions of Porteus on multiple netbooks/laptops, an a USB flash drive, I also have an x86-64 system on my netbook and a BIOS/UEFI booting USB flash drive. The Modules folder on the systems other than my netbook are considerably smaller. They primarily have firefox, flashplayer & java modules plus a game or two. No Wine modules.
[SOLVED] usm "No space left on device" with 120MB free?
Posted: 21 Sep 2017, 20:50
by postcd
Ed_P wrote: ↑22 Dec 2015, 00:08
With the changes=EXIT cheatcode the /tmp folder is not saved. Along with several others. The main thing I like with the EXIT option is if I screw up some things testing I can bypass updating the save.dat file when rebooting.
I got same issue as OP, and when used EXIT boot option as advised by Ed_P, the USM updated all databases without issue. the "/" mount point had plenty of disk space then.
I did it like this:
turned:
"changes=/porteus/porteussaveenc.dat"
to
"changes=EXIT:/porteus/porteussaveenc.dat"
in porteus.cfg (/mnt/sda1/boot/syslinux/porteus.cfg ?)
rebooted
run usm / updates / update all