Hi!
As the openSUSE updater runs, it finds many new updates (too many?) I get the following error;
mktemp: cannot make temp dir /tmp/opensuseupdaterHCOLDU49961: too many links
Why is this? The updater just quits and no new software packages are installed.
It may be, that you are running out of free space on the disk
Thanks for your reply! I thought so too, but it turns out that I have 6.7 GB free on the volume mounted as /
Even stranger is the fact that basically no program whatsoever seems to start when I run KDE and click on the menu or icons. This puzzle me alot…
Any more suggestions?
Is your file system maybe mount as read-only? You can check that using the mount command - the root / should state rw and not ro.
What is your partition layout? If you like, post the output of mount so we can see what’s listed.
Also, can you create and delete a file in the /tmp dir?
If so, you could try clearing out all files in /tmp and rebooting
as root (take care with this command not to remove something you don’t want to!):
rm -Rf /tmp/*
rm -Rf /tmp/.*
and reboot…
Hi!
No, it seems as if the / is mounted as rw. This is the layout;
/dev/sda2 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda3 on /home type ext3 (rw,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
securityfs on /sys/kernel/security type securityfs (rw)
Here is a clue; When i run rm -Rf /tmp/* I get the followin error
-bash: /bin/rm: Argument list too long
(the tmp folder is filled with files such as YaST2-32767-SW1uUX and so on. It seems as if YAST is creating an enormous amount of files the whole time it is downloading new updates…?! process y2base also changes PID all the time. Im trying to kill it…)
You could try renaming the tmp directory and recreating one with the same rights set and then reboot.
Also might be time to fschk your filesystem to be sure. You might wanna backup any important data before doing so!
before rebooting have a look at the output dmesg gives you to see if there are disk or other hw errors reported.
I dont know how, but I managed to solve the problem. What I did was basiclly the following;
However I still don´t really understand why the yast2 process just went wild. There was a new process started every few seconds, which caused the application hang and creation of thousands of /tmp/yast2_* -folders.
Thanks for all the support!
Cheers!
// H