ebrke Posted July 8, 2017 Share Posted July 8, 2017 I know very few here use openSUSE, but here goes. When I allow automatic security update to run I get this error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/4.4.74-18.20-default/kernel/drivers/ptp/ptp.ko: cpio: rename failed - No space left on deviceerror: kernel-default-4.4.74-18.20.1.x86_64: install failed Yet uname tells me:ebrke@linux-vida:~> uname -r4.4.74-18.20-default Grub also confirms at boot that kernel is 4.4.74-18.20 (I have the option of starting current and previous versions). Anyone got any ideas? Quote Link to comment Share on other sites More sharing options...
abarbarian Posted July 8, 2017 Share Posted July 8, 2017 I know very few here use openSUSE, but here goes. When I allow automatic security update to run I get this error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /lib/modules/4.4.74-18.20-default/kernel/drivers/ptp/ptp.ko: cpio: rename failed - No space left on deviceerror: kernel-default-4.4.74-18.20.1.x86_64: install failed Yet uname tells me:ebrke@linux-vida:~> uname -r4.4.74-18.20-default Grub also confirms at boot that kernel is 4.4.74-18.20 (I have the option of starting current and previous versions). Anyone got any ideas? A quick google throws up nothing. May be an enquiry at the Suse forums might be a better bet. Is your pc working ok ? Quote Link to comment Share on other sites More sharing options...
sunrat Posted July 9, 2017 Share Posted July 9, 2017 I'm guessing it's not the same kernel, 4.4.74-18.20-default vs 4.4.74-18.20.1.x86_64 This bit looks the most worrying: No space left on device Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 9, 2017 Share Posted July 9, 2017 I'm guessing it's not the same kernel, 4.4.74-18.20-default vs 4.4.74-18.20.1.x86_64 This bit looks the most worrying: No space left on device Check your partitions as one one of them is full. Run df - h This could be a misconfiguration but one of your drives is 100% full so it cannot be mounted. Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 9, 2017 Author Share Posted July 9, 2017 I did that yesterday and didn't find any partition anywhere close to 100%: Filesystem Size Used Avail Use% Mounted ondevtmpfs 1.5G 0 1.5G 0% /dev tmpfs 1.5G 0 1.5G 0% /dev/shm tmpfs 1.5G 2.4M 1.5G 1% /run tmpfs 1.5G 0 1.5G 0% /sys/fs/cgroup /dev/sda6 20G 7.4G 13G 38% / /dev/sda6 20G 7.4G 13G 38% /.snapshots /dev/sda6 20G 7.4G 13G 38% /var/cache /dev/sda6 20G 7.4G 13G 38% /var/lib/mysql /dev/sda6 20G 7.4G 13G 38% /tmp /dev/sda6 20G 7.4G 13G 38% /boot/grub2/i386-pc /dev/sda6 20G 7.4G 13G 38% /var/log /dev/sda6 20G 7.4G 13G 38% /var/lib/mariadb /dev/sda6 20G 7.4G 13G 38% /srv /dev/sda6 20G 7.4G 13G 38% /boot/grub2/x86_64-efi /dev/sda6 20G 7.4G 13G 38% /var/tmp /dev/sda6 20G 7.4G 13G 38% /var/lib/mailman /dev/sda6 20G 7.4G 13G 38% /var/lib/pgsql /dev/sda6 20G 7.4G 13G 38% /var/lib/machines /dev/sda6 20G 7.4G 13G 38% /var/lib/named /dev/sda6 20G 7.4G 13G 38% /var/spool /dev/sda6 20G 7.4G 13G 38% /opt /dev/sda6 20G 7.4G 13G 38% /var/crash /dev/sda6 20G 7.4G 13G 38% /var/opt /dev/sda6 20G 7.4G 13G 38% /usr/local /dev/sda6 20G 7.4G 13G 38% /var/lib/libvirt/images /dev/sda7 378G 2.3G 374G 1% /home tmpfs 297M 12K 297M 1% /run/user/1000 Also YAST shows install history that system is at 4.4.74-18.20.1: Everything seems to be working all right--I'm baffled. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 9, 2017 Share Posted July 9, 2017 (edited) Something is buggy about YaST I think. I had the same problem updating in Virtual Box with LEAP 42.2 and I kept aborting and reloading until everything went through. It took a long time to reboot but here I am. System: Host: linux-cizf Kernel: 4.4.74-18.20-default x86_64 (64 bit gcc: 4.8.5) Desktop: KDE Plasma 5.8.6 (Qt 5.6.1) Distro: openSUSE Leap 42.2 Machine: Device: kvm System: innotek product: VirtualBox v: 1.2 Mobo: Oracle model: VirtualBox v: 1.2 BIOS: innotek v: VirtualBox date: 12/01/2006 CPU: Dual core Intel Core i5-2320 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3) bmips: 11972 clock speeds: max: 2993 MHz 1: 2993 MHz 2: 2993 MHz Graphics: Card: InnoTek Systemberatung VirtualBox Graphics Adapter bus-ID: 00:02.0 Display Server: X.org 1.18.3 drivers: modesetting,vboxvideo (unloaded: fbdev,vesa) Resolution: 88x30 Audio: Card Intel 82801AA AC'97 Audio Controller driver: snd_intel8x0 ports: d100 d200 bus-ID: 00:05.0 Sound: Advanced Linux Sound Architecture v: k4.4.74-18.20-default Network: Card: Intel 82540EM Gigabit Ethernet Controller driver: e1000 v: 7.3.21-k8-NAPI port: d010 bus-ID: 00:03.0 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: HDD Total Size: 17.2GB (69.3% used) ID-1: /dev/sda model: VBOX_HARDDISK size: 17.2GB Partition: ID-1: / size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-2: /opt size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-3: /home size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-4: /tmp size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-5: /var/log size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-6: /var/tmp size: 14G used: 9.2G (67%) fs: btrfs dev: /dev/sda2 ID-7: swap-1 size: 2.15GB used: 0.05GB (2%) fs: swap dev: /dev/sda1 Sensors: None detected - is lm-sensors installed and configured? Info: Processes: 177 Uptime: 0:13 Memory: 1118.8/1999.5MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.3.421) inxi: 2.3.8 Edited July 9, 2017 by raymac46 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 9, 2017 Author Share Posted July 9, 2017 (edited) Sorry, Ray, not quite sure what you mean. Are you thinking my error message was a YaST problem? When you say "abort and reload" , can you tell me where you were working from--online update through YaST or the install offered through the security popup? Edited July 9, 2017 by ebrke Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 9, 2017 Share Posted July 9, 2017 Unless it is perhaps the /tmp file that is filling, I do not know what else this error would mean besides a full partition: No space left on device Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 9, 2017 Author Share Posted July 9, 2017 (edited) Agreed--that's what has me so confused and there's 13GB free on that partition. I can try to register and put the question on openSUSE's forum, but some years ago I got short shrift there and didn't go back. Guess it might have changed. Edited July 9, 2017 by ebrke 1 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 9, 2017 Share Posted July 9, 2017 Well let me if you figure it out as that is very weird. Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted July 9, 2017 Share Posted July 9, 2017 I'd post at LinuxQuestions.org before I bothered with the OpenSuse forums... https://www.linuxquestions.org/questions/suse-opensuse-60/ 1 Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 9, 2017 Share Posted July 9, 2017 I think the update process through YaST might be buggy. I was doing the typical online update when I got the "no space left" error and could not install the kernel update. I aborted the installation and ran it again in YaST...and again. Each time more packages were updated and finally the update queue was empty. I did not reboot until everything was updated and then it took a long time for the GUI to show up. I assume some modules were being installed on boot-up. Maybe the error is more general and if you try to update using the command line it will show up there as well. I don't know because I have only used YaST to update and don't know the command line procedure in SuSE. Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 9, 2017 Share Posted July 9, 2017 (edited) https://serverfault....d-enough-inodes May be a problem with btrfs. Edited July 9, 2017 by raymac46 1 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 9, 2017 Author Share Posted July 9, 2017 https://serverfault....d-enough-inodes May be a problem with btrfs. Checked the link but have to admit I haven't even heard of btrfs. I'm using ext4. Am I missing something? Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 9, 2017 Author Share Posted July 9, 2017 (edited) I think the update process through YaST might be buggy. I was doing the typical online update when I got the "no space left" error and could not install the kernel update. I aborted the installation and ran it again in YaST...and again. Each time more packages were updated and finally the update queue was empty. I did not reboot until everything was updated and then it took a long time for the GUI to show up. I assume some modules were being installed on boot-up. Maybe the error is more general and if you try to update using the command line it will show up there as well. I don't know because I have only used YaST to update and don't know the command line procedure in SuSE. There's a notification that there are patches available that pops up on the desktop. I was using that to install updates rather than actually opening YaST and running Online Update. If I'd actually gone into YaST, maybe I would have seen more detail, I don't know. Everything I can see points to the update being installed in spite of the error message--I'm assuming I can trust both uname and the YaST installation history. Very strange. Edited July 9, 2017 by ebrke Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 9, 2017 Share Posted July 9, 2017 https://serverfault....d-enough-inodes May be a problem with btrfs. Checked the link but have to admit I haven't even heard of btrfs. I'm using ext4. Am I missing something? I am using btrfs according to my disk info. Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 10, 2017 Share Posted July 10, 2017 I have heard of it but never tried it. The odd part is why would OpenSuse choose it as their default? Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 10, 2017 Share Posted July 10, 2017 https://en.opensuse.org/SDB:BTRFS I guess they want to have rollback facility like Windows System Restore. Not worth the aggravation if you ask me - but nobody did. 3 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 10, 2017 Author Share Posted July 10, 2017 (edited) https://en.opensuse.org/SDB:BTRFS I guess they want to have rollback facility like Windows System Restore. Not worth the aggravation if you ask me - but nobody did. Crap. You're right--it's btrfs. I completely missed this during my last install. In addition to CLI instructions in your link, there's now an entry for Snapper in YaST under Miscellaneous. I can see all the snapshots but haven't a clue which, if any, I can delete safely. Have to do more research I guess. Why the *** do they just keep creating snapshots if it's going to give you problems? After 10+ years, this is the first time SUSE has really messed me up. Really don't need this today--had dealings with Comcast about new TV set top box in mother's bedroom that wouldn't activate properly and the top of my head is ready to blow off now.EDIT: All SUSE says in documentation is to delete oldest snapshots first since they take up most space, not a word about what might be more important or shouldn't be deleted. When I feel stronger I'll have to try deleting all but last couple of snapshots and keep checking and deleting as time goes on. What a pain. Annoying as all this is, I have to say that I knew someone here would come up with the answer. Thanks everyone! Can I use gparted to increase the space I have allocated to / without needing to do a complete reinstall afterward? I'm having a senior moment, I guess, but something nags at me that I shouldn't do it although I can't remember why. Edited July 10, 2017 by ebrke 1 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 10, 2017 Share Posted July 10, 2017 You should be just fine resizing the / partition but you will to do this via a livecd/dvd. 1 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 10, 2017 Author Share Posted July 10, 2017 You should be just fine resizing the / partition but you will to do this via a livecd/dvd. I'd use GParted dvd I burned a couple of years ago. Hope that version supports btrfs--wikipedia says GParted will handle all operations on btrfs. Anyone have a link to download GParted if I need newest version? Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 10, 2017 Share Posted July 10, 2017 http://gparted.org/ 1 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 10, 2017 Author Share Posted July 10, 2017 (edited) http://gparted.org/ Duh, never occurred to me. Edited July 10, 2017 by ebrke 2 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 10, 2017 Share Posted July 10, 2017 http://gparted.org/ Duh, never occurred to me. Hehe Quote Link to comment Share on other sites More sharing options...
raymac46 Posted July 10, 2017 Share Posted July 10, 2017 I've deleted Leap 42.2 from VirtualBox. It just doesn't seem to be an appropriate distro to run with limited storage capacity like you have in a VM. Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 10, 2017 Author Share Posted July 10, 2017 I've deleted Leap 42.2 from VirtualBox. It just doesn't seem to be an appropriate distro to run with limited storage capacity like you have in a VM. I'm going to go with deleting snapshots and increasing the size of my / partition. Like I said before, I'm really annoyed by this--wonder if I would have had the opportunity to change the fs to something other than btrfs during the install if I had realized what was happening. Will definitely look at that next time (which could be sooner rather than later if anything goes wrong with partition resizing). Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted July 10, 2017 Share Posted July 10, 2017 Take a deep breath and just reinstall OpenSuse on EXT4. You'll be happier in the long run. 1 Quote Link to comment Share on other sites More sharing options...
securitybreach Posted July 10, 2017 Share Posted July 10, 2017 Take a deep breath and just reinstall OpenSuse on EXT4. You'll be happier in the long run. Agreed 1 Quote Link to comment Share on other sites More sharing options...
abarbarian Posted July 11, 2017 Share Posted July 11, 2017 This article from 2016 my help with your decision. Using Btrfs for Easy Backup and Rollback After finishing up the rest of the install and rebooting, regular snapshots can be setup with snapper, a btrfs snapshot utility made by SUSE which does regular snapshot and cleanup. This creates a new subvolume “.snapshots” at the root of the specified subvolume. Snapper has a utility to help you roll back; however, it is inherently flawed and can mess up your file system layout due to how it rolls back. To avoid this issue, delete the new subvolume snapper just made. Instead create a new subvolume under the “snapshots” subvolume for whichever subvolumes are being snapshotted by snapper. Since snapshots are not backups it’s also important a good backup is in place in addition to having snapshots. The backup solution I found is Btrbk, a very configurable backup solution written in perl. Btrbk was an easy install for me as it was in the Arch User Repository, Btrbk (AUR). It came with great documentation, as well as systemd timers and services. Btrbk takes snapshots and then backs up the selected snapshot to a variety of backup locations. The snapshots can then be chosen to be kept or deleted based on a set amount of time. I’ve been using this system for several months with no problems. I have rolled back several times and it has been as easy as booting into another Linux distro on my computer, and moving around snapshots. This could probably be automated in such a way that at boot a subvolume is chosen to be the volume booted into. This is what Snapper tried to achieve but the way it does it is very messy as the resulting subvolume ends up being in the wrong place. This problem is not simple to fix as snapshots are read-only so somewhere along the line another snapshot has to be taken that is read-write for the system to be usable. Once a solution arrives for this Btrfs will have a feature similar to ZFS boot environments. I’m looking forward to this. Thus far I have not had any file corruption that I am aware of and I am happy with the resulting system. I have yet to use ZFS on Linux as my system root, but I’m looking forward to comparing the two when I finally get my problems ironed out. Overall the future with btrfs looks interesting and I will be keeping an eye on it. Another fine example of the KISS principle To be fair btrfs once all the bugs have been sorted should be of value to business users a sit looks like it uses less resources and should be very quick in use. However it looks pretty darn complicated for the average user at this stage. With ssd's and fairly modern hardware backing up a root partition of 20 GB takes 10 to 20 minutes and is a pretty easy task to set up so does the average user really need the bells and whistles of this newcomer ? 2 Quote Link to comment Share on other sites More sharing options...
ebrke Posted July 11, 2017 Author Share Posted July 11, 2017 (edited) Why SUSE took this default for Leap is beyond me. Doing it for Tumbleweed would make more sense--Leap is supposed to be the stable one btrfs doesn't seem to fit that category yet. I hope that they allow the option of using a different file system during the install, I didn't really look at the root partition in the Advanced Setup since I'm used to concentrating on being sure my /home will just be mounted intact. Forcing people into this with no other option allowed might really turn users off. I took a quick look at the documentation for snapper--yuck. If something went that badly wrong, I'd just as soon do a net reinstall--takes maybe 45 minutes and you'd have a clean system at the end. Edited July 11, 2017 by ebrke Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.