Re: Upgrading Kernel - Out of Disk Space
Gary Dale a écrit : $ df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/lapsdeb-root 314M 237M 57M 81% / /dev/mapper/lapsdeb-var 2.7G 318M 2.3G 13% /var /dev/mapper/lapsdeb-usr 8.2G 2.6G 5.2G 34% /usr /dev/mapper/lapsdeb-tmp 360M 2.1M 335M 1% /tmp /dev/sda1 228M 21M 196M 10% /boot /dev/mapper/lapsdeb-home 274G 8.5G 252G 4% /home That is an unusual file system. Unfortunately not. It's the result of the Debian installer automatic partitioner when you choose to separate all main system directories. It is broken in several ways : - / is too small for current kernels ; - /usr, /tmp and /var may be too small too ; - when using LVM, it does not reserve any free space for future allocation/resizing. For these reasons and others, I never use the automatic partitioner. The problem is that your / partition only has 314M allocated to it. This is ridiculously small. I understand people use LVM because it supposedly makes adding more space easier. Figure out how to use LVM to increase your / allocation to something more reasonable. 20G is what I would normally use as a minimum, with more for desktop use. You've got 252G free on /home. Shifting some of that over to / would do wonders. First, check if you cannot free some (~100 MB) space in the / filesystem (/root, /srv, /opt). Otherwise, you can extend a mounted ext2/3/4 filesystem on an LVM logical volume. However you cannot reduce an ext mounted filesystem. Boot in rescue mode. Unmount /home. Reduce /dev/mapper/lapsdeb-home filesystem with resize2fs or relevant tool. Reduce /dev/mapper/lapsdeb-home logical volume with lvreduce. Extend /dev/mapper/lapsdeb-root logical volume with lvextend. Extend /dev/mapper/lapsdeb-root filesystem with resize2fs or relevant tool. Mount /home. Exit rescue mode and resume system start (ctrl+d). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54df1f44.3020...@plouf.fr.eu.org
Re: / and separate partitions (was) Re: Upgrading Kernel - Out of Disk Space
Iain M Conochie a écrit : Having said that, with 100GB disks common now, the fallacy that, just because you cannot have a sub 1G / filesystem, that you have to place /usr onto that partition, is annoying. In fact, the whole /usr merge to me is annoying. There is no /usr merge requirement. The only requirement is that /usr should be available earlier than it used to be, so it should be mounted in the initramfs instead of the init process. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54df1ad2.3080...@plouf.fr.eu.org
Re: Upgrading Kernel - Out of Disk Space
On 2015-02-14, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Otherwise, you can extend a mounted ext2/3/4 filesystem on an LVM logical volume. However you cannot reduce an ext mounted filesystem. He said this was an encrypted lvm file system, so I believe there's a few more steps involved (although I really know nothing about it). https://help.ubuntu.com/community/ResizeEncryptedPartitions Boot in rescue mode. Unmount /home. Reduce /dev/mapper/lapsdeb-home filesystem with resize2fs or relevant tool. Reduce /dev/mapper/lapsdeb-home logical volume with lvreduce. Extend /dev/mapper/lapsdeb-root logical volume with lvextend. Extend /dev/mapper/lapsdeb-root filesystem with resize2fs or relevant tool. Mount /home. Exit rescue mode and resume system start (ctrl+d). -- “True terror is to wake up one morning and discover that your high school class is running the country.” – Kurt Vonnegut -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmdv2g5.226.cu...@einstein.electron.org
Re: Upgrading Kernel - Out of Disk Space
Curt a écrit : On 2015-02-14, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Otherwise, you can extend a mounted ext2/3/4 filesystem on an LVM logical volume. However you cannot reduce an ext mounted filesystem. He said this was an encrypted lvm file system, so I believe there's a few more steps involved (although I really know nothing about it). No. https://help.ubuntu.com/community/ResizeEncryptedPartitions The logical volumes to be resized are not encrypted. Only the physical volume is encrypted, and does not need to be resized. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54df9b5b.60...@plouf.fr.eu.org
Re: Upgrading Kernel - Out of Disk Space
On 2015-02-14, Pascal Hambourg pas...@plouf.fr.eu.org wrote: He said this was an encrypted lvm file system, so I believe there's a few more steps involved (although I really know nothing about it). No. https://help.ubuntu.com/community/ResizeEncryptedPartitions The logical volumes to be resized are not encrypted. Only the physical volume is encrypted, and does not need to be resized. I take it back then. Sorry. -- “True terror is to wake up one morning and discover that your high school class is running the country.” – Kurt Vonnegut -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmdv8l4.226.cu...@einstein.electron.org
Re: Upgrading Kernel - Out of Disk Space
Stephen R Guglielmo wrote: I updated my apt repo and there was a kernel update. I ran the update, and received an error claiming no space left on device. Normally, I would do a force-uninstall for the currently running kernel (freeing space), then install the new kernel and reboot. However, this is an update, not a replacement. I'm not sure how to proceed. When I installed this system, I selected automatic partitioning with an encrypted LVM, so I imagine resizing the partition would prove difficult. I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. This is on Debian Jessie. FilesystemSize Used Avail Use% Mounted on /dev/mapper/lapsdeb-root 314M 237M 57M 81% / Very small. /dev/mapper/lapsdeb-home 274G 8.5G 252G 4% /home Very large. (The default for the debian-installer is to give all of the remaining space to the last partiton. IMNHO that is bad.) /dev/mapper/lapsdeb-usr 8.2G 2.6G 5.2G 34% /usr Using less than 3G for /usr. If it were me I would back up /home to some place else. Verify that /home is backed up. Then I would lvremove /dev/lapsdeb/home to free up that large amount of disk space. Having that free disk space available for use I would then 'lvextend -L+3G /dev/lapsdeb/root' to add some of that space to it. Use 'resize2fs /dev/lapsdeb/root' to do an online expansion of the root file system to the now larger space. Then I would 'lvcreate -L100G -nlapsdeb home' to create a new /home partition. Use mkfs to create the file system. Mount it. Then restore /home from backup. That would give a fully working system rather easily without need for re-installing anything. (Other than the backup and restore of /home to reclaim some of that space.) Sizes are of course open for changes. /home is only using 8.5G now. I start with 100G and be flexible from there. that would leave somewhere around 150G of free space in LVM available for future online expansion whenever needed. LVM works very nicely for expanding space and resize2fs can increase the size of file systems online. Works very well. Shrinking filesystems with resize2fs on the other hand does not work well. Avoid shrinking. That is why I would backup, remove, recreate, restore rather than shrinking. My Wheezy 7 media machine has a little more than 3G in /usr. When using a separate /usr the root partition doesn't need to be very big at all. Filesystem Size Used Avail Use% Mounted on rootfs 5.5G 643M 4.6G 13% / /dev/mapper/v6-usr28G 3.2G 23G 13% /usr As you can see I have not bothered with converging / and /usr together yet on my machine. At some point I might be forced into do so. If I were then I would expand the root fs as much as needed then boot using the debian-installer in rescue mode then copy the /usr partition up to / and remove the /usr partition and the entry from /etc/fstab. Then reboot to the new system without a separate /usr. (Creating a separate /usr is the same thing in reverse.) This kind of file system surgery with LVM and resize2fs is actually quite easy. It is however file system surgery and as with any surgery care must be taken to ensure a good result. Not for the faint of heart. Always make sure you have a good full backup in case a mistake is made along the way. Bob signature.asc Description: Digital signature
Re: Upgrading Kernel - Out of Disk Space
Stephen R Guglielmo: On Thu, 12 Feb 2015 10:46:35 +0100 Jochen Spieker m...@well-adjusted.de wrote: Stephen R Guglielmo: I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. There's been several complaints about similar issues on this list. I am not sure whether there were any recent changes in debian-installer to solve that. Now there's still time to report bugs before jessie is released. So it's recommended that I file a bug report regarding this? If it bugs you, why not? It's obviously an issue to anyone who uses the encrypted auto-partition option in d-i. I think this is even independent of encryption. J. -- When standing at the top of beachy head I find the rocks below very attractive. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Upgrading Kernel - Out of Disk Space
what version of the installer are you using? if it is an older image i'd try the most recent before filing bugs. songbird -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/s7j1rb-s12@id-306963.user.uni-berlin.de
Re: Upgrading Kernel - Out of Disk Space
On Wed, 11 Feb 2015 23:55:42 -0500 Gary Dale garyd...@torfree.net wrote: On 11/02/15 10:01 PM, Stephen R Guglielmo wrote: Hi list, I updated my apt repo and there was a kernel update. I ran the update, and received an error claiming no space left on device. Normally, I would do a force-uninstall for the currently running kernel (freeing space), then install the new kernel and reboot. However, this is an update, not a replacement. I'm not sure how to proceed. When I installed this system, I selected automatic partitioning with an encrypted LVM, so I imagine resizing the partition would prove difficult. I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. This is on Debian Jessie. Thanks! --- Preparing to unpack .../linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb ... Unpacking linux-image-3.16.0-4-amd64 (3.16.7-ckt4-3) over (3.16.7-ckt2-1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb (--unpack): cannot copy extracted data for './lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/lpfc/lpfc.ko' to '/lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/lpfc/lpfc.ko.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- $ df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/lapsdeb-root 314M 237M 57M 81% / udev 10M 0 10M 0% /dev tmpfs 776M 8.8M 767M 2% /run tmpfs 1.9G 4.0K 1.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/lapsdeb-var 2.7G 318M 2.3G 13% /var /dev/mapper/lapsdeb-usr 8.2G 2.6G 5.2G 34% /usr /dev/mapper/lapsdeb-tmp 360M 2.1M 335M 1% /tmp /dev/sda1 228M 21M 196M 10% /boot /dev/mapper/lapsdeb-home 274G 8.5G 252G 4% /home tmpfs 388M 4.0K 388M 1% /run/user/1000 That is an unusual file system. The out of space error is on your / partition, which would also hold /lib where the modules are being unpacked. I don't use LVM myself so I'm not familiar with it but I'm guessing it's providing all the /dev/mapper devices. The problem is that your / partition only has 314M allocated to it. This is ridiculously small. I understand people use LVM because it supposedly makes adding more space easier. Figure out how to use LVM to increase your / allocation to something more reasonable. 20G is what I would normally use as a minimum, with more for desktop use. You've got 252G free on /home. Shifting some of that over to / would do wonders. It was until fairly recently general practice to allocate a few hundred MB to / if /usr and /var were separate. It's only in the last few years that the size of /lib/modules has really exploded, and /usr now needs (in practice) to physically live under /. On a sid workstation with ~4000 packages installed including three kernels, with everything except /home and /boot under /, I have the following usage: /boot 42M /lib 0.55G /lib/modules 0.5G /usr 7.65G /var 1.87G all / 11.1G -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150212184932.69063...@jresid.jretrading.com
Re: Upgrading Kernel - Out of Disk Space
On 2015-02-12, Reco recovery...@gmail.com wrote: You're right in the case of conventional LVM. But OP is using an encrypted one, and resizing an encrypted LV is much more complex (it requires lvresize, cryptmount and resize2fs in the right sequence). It's presumably possible (never done it personally), but complex. This is good to know. However I don't understand what you get for your money using an encrypted *LVM* file system if the commodity of resizing (or reallocation) is more or less removed from the picture. -- “True terror is to wake up one morning and discover that your high school class is running the country.” – Kurt Vonnegut -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmdosv4.2ap.cu...@einstein.electron.org
Re: Upgrading Kernel - Out of Disk Space
On Thu, Feb 12, 2015 at 09:35:32AM +, Curt wrote: On 2015-02-12, Reco recovery...@gmail.com wrote: You're right in the case of conventional LVM. But OP is using an encrypted one, and resizing an encrypted LV is much more complex (it requires lvresize, cryptmount and resize2fs in the right sequence). It's presumably possible (never done it personally), but complex. This is good to know. However I don't understand what you get for your money using an encrypted *LVM* file system if the commodity of resizing (or reallocation) is more or less removed from the picture. Using LVM-on-encryption means that you only need one key (one password) to unlock the system. The alternative (encrypted LVs or partitions) would mean separate keys for each file system and managing that would be quite a task. So, while LVM can give you resizing, in this case it's being used for it's partition-upon-a-partition capabilities. -- “True terror is to wake up one morning and discover that your high school class is running the country.” – Kurt Vonnegut -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmdosv4.2ap.cu...@einstein.electron.org signature.asc Description: Digital signature
Re: Upgrading Kernel - Out of Disk Space
On Thursday 12 February 2015 09:46:35 Jochen Spieker wrote: I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. There's been several complaints about similar issues on this list. I am not sure whether there were any recent changes in debian-installer to solve that. Now there's still time to report bugs before jessie is released. This has gone on for years, ever since I have installed Debian. Someone (some people) among the debian-installer developers must, I think, regard it as a feature, not a bug. It forced me into manual partitioning several versions back. Before that, I used to solve the problem by partitioning with the PCLinuxOS installer before installing Debian. At that time, I couldn't understand dedicated partitioners. ;-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502121131.43584.lisi.re...@gmail.com
Re: Upgrading Kernel - Out of Disk Space
On Thursday 12 February 2015 11:31:43 Lisi Reisz wrote: On Thursday 12 February 2015 09:46:35 Jochen Spieker wrote: I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. There's been several complaints about similar issues on this list. I am not sure whether there were any recent changes in debian-installer to solve that. Now there's still time to report bugs before jessie is released. This has gone on for years, ever since I have installed Debian. Someone (some people) among the debian-installer developers must, I think, regard it as a feature, not a bug. It forced me into manual partitioning several versions back. Before that, I used to solve the problem by partitioning with the PCLinuxOS installer before installing Debian. At that time, I couldn't understand dedicated partitioners. ;-) Lisi Yeah, yeah. The partitioner provides ridiculous scheme. I moved my root to another disk partition so I can keep more than one kernel. Since the partitioner gave most all the 1 terra to /home, I have /opt and /usr/local bound to directories on that partition. Really absurd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2307065.1ZSU8pqsdW@dovidhalevi
Re: Upgrading Kernel - Out of Disk Space
On Thu, 12 Feb 2015 10:46:35 +0100 Jochen Spieker m...@well-adjusted.de wrote: Stephen R Guglielmo: I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. There's been several complaints about similar issues on this list. I am not sure whether there were any recent changes in debian-installer to solve that. Now there's still time to report bugs before jessie is released. So it's recommended that I file a bug report regarding this? It's obviously an issue to anyone who uses the encrypted auto-partition option in d-i. pgpbRmd81CEWB.pgp Description: OpenPGP digital signature
/ and separate partitions (was) Re: Upgrading Kernel - Out of Disk Space
snip It was until fairly recently general practice to allocate a few hundred MB to / if /usr and /var were separate. It's only in the last few years that the size of /lib/modules has really exploded, and /usr now needs (in practice) to physically live under /. I once tried to put /lib/modules under it's own partition. Needless to say, it broke horribly and the system was unable to boot. Having said that, with 100GB disks common now, the fallacy that, just because you cannot have a sub 1G / filesystem, that you have to place /usr onto that partition, is annoying. In fact, the whole /usr merge to me is annoying. If we do not _need_ /usr, why have it in the first place? Why have this separate directory that you should no longer split off onto a separate partition? Just have everything in / Iain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54dd4065.7020...@thargoid.co.uk
Re: Upgrading Kernel - Out of Disk Space
Taking a look into /lib/modules could tell if any older (possibly dispensible) kernel versions are present on your system. Regards, jvp. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mbhtcp$9me$1...@ger.gmane.org
Re: Upgrading Kernel - Out of Disk Space
Stephen R Guglielmo: I updated my apt repo and there was a kernel update. I ran the update, and received an error claiming no space left on device. Normally, I would do a force-uninstall for the currently running kernel (freeing space), then install the new kernel and reboot. However, this is an update, not a replacement. Are you sure about that? And even if this is the case: you can still uninstall the running kernel. I would be very surprised if the new version uses 50MB more space in / than the old one. I'm not sure how to proceed. When I installed this system, I selected automatic partitioning with an encrypted LVM, so I imagine resizing the partition would prove difficult. You just need to make sure to do things in the right order, top down. It looks like you have one big encrypted LUKS container which holds one PV, VG and several LVs. If this is the case you do not need to care about LUKS because you only operate inside the container. But you would need to show your /etc/crypttab and output of pvs, vgs, lvs. I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. There's been several complaints about similar issues on this list. I am not sure whether there were any recent changes in debian-installer to solve that. Now there's still time to report bugs before jessie is released. J. -- My drug of choice is self-pity. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Upgrading Kernel - Out of Disk Space
On 2015-02-12, Darac Marjal mailingl...@darac.org.uk wrote: This is good to know. However I don't understand what you get for your money using an encrypted *LVM* file system if the commodity of resizing (or reallocation) is more or less removed from the picture. Using LVM-on-encryption means that you only need one key (one password) to unlock the system. The alternative (encrypted LVs or partitions) would mean separate keys for each file system and managing that would be quite a task. So, while LVM can give you resizing, in this case it's being used for it's partition-upon-a-partition capabilities. I see. Thank you. -- “True terror is to wake up one morning and discover that your high school class is running the country.” – Kurt Vonnegut -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmdpkpl.329.cu...@einstein.electron.org
Re: Upgrading Kernel - Out of Disk Space
Hi. On Wed, 11 Feb 2015 23:55:42 -0500 Gary Dale garyd...@torfree.net wrote: The problem is that your / partition only has 314M allocated to it. This is ridiculously small. I understand people use LVM because it supposedly makes adding more space easier. You're right in the case of conventional LVM. But OP is using an encrypted one, and resizing an encrypted LV is much more complex (it requires lvresize, cryptmount and resize2fs in the right sequence). It's presumably possible (never done it personally), but complex. Figure out how to use LVM to increase your / allocation to something more reasonable. 20G is what I would normally use as a minimum, with more for desktop use. Why? OP is using separate LVs for /usr and /var, so those 20G would be a dead weight. 2G for / would be plenty. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150212093739.6d91fdb42be29b760c584...@gmail.com
Re: Upgrading Kernel - Out of Disk Space
On 11/02/15 10:01 PM, Stephen R Guglielmo wrote: Hi list, I updated my apt repo and there was a kernel update. I ran the update, and received an error claiming no space left on device. Normally, I would do a force-uninstall for the currently running kernel (freeing space), then install the new kernel and reboot. However, this is an update, not a replacement. I'm not sure how to proceed. When I installed this system, I selected automatic partitioning with an encrypted LVM, so I imagine resizing the partition would prove difficult. I'm not sure why the automatic partitioner didn't provide for enough space for future updates. See below for the relevant logs. This is on Debian Jessie. Thanks! --- Preparing to unpack .../linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb ... Unpacking linux-image-3.16.0-4-amd64 (3.16.7-ckt4-3) over (3.16.7-ckt2-1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb (--unpack): cannot copy extracted data for './lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/lpfc/lpfc.ko' to '/lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/lpfc/lpfc.ko.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt4-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- $ df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/lapsdeb-root 314M 237M 57M 81% / udev 10M 0 10M 0% /dev tmpfs 776M 8.8M 767M 2% /run tmpfs 1.9G 4.0K 1.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/lapsdeb-var 2.7G 318M 2.3G 13% /var /dev/mapper/lapsdeb-usr 8.2G 2.6G 5.2G 34% /usr /dev/mapper/lapsdeb-tmp 360M 2.1M 335M 1% /tmp /dev/sda1 228M 21M 196M 10% /boot /dev/mapper/lapsdeb-home 274G 8.5G 252G 4% /home tmpfs 388M 4.0K 388M 1% /run/user/1000 That is an unusual file system. The out of space error is on your / partition, which would also hold /lib where the modules are being unpacked. I don't use LVM myself so I'm not familiar with it but I'm guessing it's providing all the /dev/mapper devices. The problem is that your / partition only has 314M allocated to it. This is ridiculously small. I understand people use LVM because it supposedly makes adding more space easier. Figure out how to use LVM to increase your / allocation to something more reasonable. 20G is what I would normally use as a minimum, with more for desktop use. You've got 252G free on /home. Shifting some of that over to / would do wonders. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54dc324e.2040...@torfree.net
