DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to upgrade my Debian from Jessie to Stretch. apt-get upgrade worked fine. Half-way during apt-get dist-upgrade I got some errors that the installation [I'm not sure at which step, but some step after downloading] couldn't create pipes because there was no space left on the device. I checked and my root filesystem is running out of inodes. /var and /home are on different filesystems, and have plenty of space/inodes. /tmp is FORCRYINGOUTLOUD not mounted as tmpfs, and "systemctl enable tmp.mount" says the file doesn't exist. (Thank you, systemd.)
Is my only option rebuilding a filesystem with more inodes, or is there some other thing I could try?
[update]
My system has become severely crippled (i.e. only rescue mode, even unable to establish an internet connection). Unless some guru likes the challenge of bringing this system back from the dead, I will reinstall. So hint for people running into this problem in the future: do not reboot.
If you can't delete sufficient files you will have to reformat the filesystem.
I don't do Debian, but if /tmp ain't on tmpfs, it ain't the fault of systemd - I've been using it on other systems for years. Perhaps you should give the (Devian) devs a nudge.
My system wasn't dead; I just didn't configure /tmp properly i.e. typo in fstab. I was peeved, because I was told systemctl enable tmp.mount would suffice. Instead you have to edit fstab, which might have been obvious, if there wasn't systemd. Devuan is a commendable project, but there are too many borderline unsupported programs I use already.
So the main difficulty was that /var and /home, the main candidates for pruning, had their own filesystem. I removed packages that were already queued for removal with "dpkg -r {package names}". Also I looked for programs as candidates for removal, and the Steam launcher was a good one. There weren't any other obvious contenders; it was the only program that had many files in a single package.
Eventually I used a live disk. With that I could relocate /usr to another partition. (gdisk, mkfs, cp -a, edit fstab). NB: I made a back-up of my root partition BUT I should have made a back-up of /var too, since it was on another partition. I wanted to update my system before moving it to a new filesystem/partition, because I wanted to use the new inline_data support for ext4. (I had to go through most of the trouble anyway.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.