[opensuse] resize root drive
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse. My root partition is almost completely full, and I am wondering what I can do about it to make more space. Here is the layout of the drive: tribetrekDell:/ # fdisk -l Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2C1BF30F-7D76-4D8E-A2CB-FD86115234B3 Device Start End Sectors Size Type /dev/sda1 2048 411647 409600 200M EFI System /dev/sda2 411648 444415 32768 16M Microsoft reserved /dev/sda3 444416 133564415 133120000 63.5G Microsoft basic data /dev/sda4 935960576 937701375 1740800 850M Windows recovery environment /dev/sda5 133564416 146245631 12681216 6G Linux swap /dev/sda6 146245632 193349631 47104000 22.5G Linux filesystem /dev/sda7 193349632 240453631 47104000 22.5G Linux filesystem /dev/sda8 240453632 935960575 695506944 331.7G Linux filesystem Partition table entries are not in disk order. I have 2 root drives, both 22.5G, for the purpose of when the time comes to upgrade, having the previous version backed up in order to be able to boot into my system if the upgrade fails, or I have some other kind of major failure. It has saved my back many times. So, I want to keep the 22.5G drives equally sized, and I don't want to reduce the "home" partition of 331.7G. I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive, split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room. Is that something that is even possible? Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running? I don't really know the best course of action here. Any help is greatly appreciated. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/02/2018 05:32 PM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
My root partition is almost completely full, and I am wondering what I can do about it to make more space.
Here is the layout of the drive:
tribetrekDell:/ # fdisk -l Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2C1BF30F-7D76-4D8E-A2CB-FD86115234B3
Device Start End Sectors Size Type /dev/sda1 2048 411647 409600 200M EFI System /dev/sda2 411648 444415 32768 16M Microsoft reserved /dev/sda3 444416 133564415 133120000 63.5G Microsoft basic data /dev/sda4 935960576 937701375 1740800 850M Windows recovery environment /dev/sda5 133564416 146245631 12681216 6G Linux swap /dev/sda6 146245632 193349631 47104000 22.5G Linux filesystem /dev/sda7 193349632 240453631 47104000 22.5G Linux filesystem /dev/sda8 240453632 935960575 695506944 331.7G Linux filesystem
Partition table entries are not in disk order.
I have 2 root drives, both 22.5G, for the purpose of when the time comes to upgrade, having the previous version backed up in order to be able to boot into my system if the upgrade fails, or I have some other kind of major failure. It has saved my back many times.
So, I want to keep the 22.5G drives equally sized, and I don't want to reduce the "home" partition of 331.7G.
I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive, split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room.
Is that something that is even possible?
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
I don't really know the best course of action here. Any help is greatly appreciated.
I forgot to mention that I am only using ext4, not btfrs. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/18 11:40, George from the tribe wrote:
On 03/02/2018 05:32 PM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
My root partition is almost completely full, and I am wondering what I can do about it to make more space.
Here is the layout of the drive:
tribetrekDell:/ # fdisk -l Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2C1BF30F-7D76-4D8E-A2CB-FD86115234B3
Device Start End Sectors Size Type /dev/sda1 2048 411647 409600 200M EFI System /dev/sda2 411648 444415 32768 16M Microsoft reserved /dev/sda3 444416 133564415 133120000 63.5G Microsoft basic data /dev/sda4 935960576 937701375 1740800 850M Windows recovery environment /dev/sda5 133564416 146245631 12681216 6G Linux swap /dev/sda6 146245632 193349631 47104000 22.5G Linux filesystem /dev/sda7 193349632 240453631 47104000 22.5G Linux filesystem /dev/sda8 240453632 935960575 695506944 331.7G Linux filesystem
Partition table entries are not in disk order.
I have 2 root drives, both 22.5G, for the purpose of when the time comes to upgrade, having the previous version backed up in order to be able to boot into my system if the upgrade fails, or I have some other kind of major failure. It has saved my back many times.
So, I want to keep the 22.5G drives equally sized, and I don't want to reduce the "home" partition of 331.7G.
I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive, split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room.
Is that something that is even possible?
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
I don't really know the best course of action here. Any help is greatly appreciated.
I forgot to mention that I am only using ext4, not btfrs.
I lost half my ram a few days ago and while I wait for a replacement I decided to make a swap partition on my external usb3 Microsoft basic data 1T drive. I used a virtual box windows 7 to do the job, you'll find it much easier using a proper windows installation. Simply open the management console and select disk manager then do a defrag on the partition you want to shrink. All you have to do next is right click on the partition map and select shrink. In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast. Hope this helps, Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/18 10:22, Dave Plater wrote:
On 02/03/18 11:40, George from the tribe wrote:
On 03/02/2018 05:32 PM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
My root partition is almost completely full, and I am wondering what I can do about it to make more space.
Here is the layout of the drive:
tribetrekDell:/ # fdisk -l Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2C1BF30F-7D76-4D8E-A2CB-FD86115234B3
Device Start End Sectors Size Type /dev/sda1 2048 411647 409600 200M EFI System /dev/sda2 411648 444415 32768 16M Microsoft reserved /dev/sda3 444416 133564415 133120000 63.5G Microsoft basic data /dev/sda4 935960576 937701375 1740800 850M Windows recovery environment /dev/sda5 133564416 146245631 12681216 6G Linux swap /dev/sda6 146245632 193349631 47104000 22.5G Linux filesystem /dev/sda7 193349632 240453631 47104000 22.5G Linux filesystem /dev/sda8 240453632 935960575 695506944 331.7G Linux filesystem
Partition table entries are not in disk order.
I have 2 root drives, both 22.5G, for the purpose of when the time comes to upgrade, having the previous version backed up in order to be able to boot into my system if the upgrade fails, or I have some other kind of major failure. It has saved my back many times.
So, I want to keep the 22.5G drives equally sized, and I don't want to reduce the "home" partition of 331.7G.
I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive, split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room.
Is that something that is even possible?
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
I don't really know the best course of action here. Any help is greatly appreciated.
I forgot to mention that I am only using ext4, not btfrs.
I lost half my ram a few days ago and while I wait for a replacement I decided to make a swap partition on my external usb3 Microsoft basic data 1T drive. I used a virtual box windows 7 to do the job, you'll find it much easier using a proper windows installation. Simply open the management console and select disk manager then do a defrag on the partition you want to shrink. All you have to do next is right click on the partition map and select shrink.
In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast. Hope this helps,
If he's not using LVM already, then LVM will be no use ... What you need is something like Windows Partition Magic. I'm sure there must be a linux equivalent, but your big problem will be shrinking your big Windows partition. Also, you need to get VERY clear in your head the difference between PARTITION size, and FILESYSTEM size. You need to shrink the ntfs filesystem, and then shrink the partition to match. You can just delete and recreate the swap, that won't be a problem, If the first root partition is your spare, you could delete and recreate it, Otherwise, you will need to move the partition AND filesystem down. There's absolutely no problem with increasing the size of the partition - it's when you move the base of the partition that things gets confused if you're not careful. You could then move down or recreate your second root partition as you see fit. If you reboot, having moved/resized your PARTITIONS, you won't notice any change in disk size. You'll need to run resize2fs to add all that new partition space into the file system. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-02 11:22, Dave Plater wrote:
In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast.
This is far from trivial. Needs backup, repartition, format, recover from backup, reinstall grub. Which is, anyway, what I would do, but without LVM. There were tools in Windows that could move partitions around, but I'm unsure in Linux. I think there was one, but I never tried. It is possible to grow a partition, at the end of it. The only possibility without moving things is to add a /usr or /usr/something partition. And I would not do that. I would go the backup, repartition, restore route. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-03-02 11:22, Dave Plater wrote:
In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast.
This is far from trivial. Needs backup, repartition, format, recover from backup, reinstall grub.
Which is, anyway, what I would do, but without LVM.
There were tools in Windows that could move partitions around, but I'm unsure in Linux. I think there was one, but I never tried. It is possible to grow a partition, at the end of it.
The only possibility without moving things is to add a /usr or /usr/something partition. And I would not do that. I would go the backup, repartition, restore route.
TBH, my approach would be to dump the double system partition 'for future updates'. I've done that, too, in the past - and mostly regretted it later. If you want to test a new install, you might as well do it with a separate USB disk, and when fine, move that one to the main disk (or do a dup/reinstall). Then you'd only have to combine the two consecutive partitions, which is relatively easy if your current system is in the lower one. (also, moving a system to a different partition is really easy with btrfs - you might consider that for a new install....) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-02 12:22, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 2018-03-02 11:22, Dave Plater wrote:
TBH, my approach would be to dump the double system partition 'for future updates'. I've done that, too, in the past - and mostly regretted it later.
If you want to test a new install, you might as well do it with a separate USB disk, and when fine, move that one to the main disk (or do a dup/reinstall).
Yep, if you have USB3 and an external SSD.
Then you'd only have to combine the two consecutive partitions, which is relatively easy if your current system is in the lower one.
Yep.
(also, moving a system to a different partition is really easy with btrfs - you might consider that for a new install....)
What if they decide to create a new layout, as has happened in TW? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-03-02 12:22, Peter Suetterlin wrote:
If you want to test a new install, you might as well do it with a separate USB disk, and when fine, move that one to the main disk (or do a dup/reinstall).
Yep, if you have USB3 and an external SSD.
For testing even USB2 would be enough, but yes, you're right ;^>
(also, moving a system to a different partition is really easy with btrfs - you might consider that for a new install....)
What if they decide to create a new layout, as has happened in TW?
You can adapt/change that. My TW machines only have @/var, without reinstall... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/18 13:12, Carlos E. R. wrote:
On 2018-03-02 11:22, Dave Plater wrote:
In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast.
This is far from trivial. Needs backup, repartition, format, recover from backup, reinstall grub.
Which is, anyway, what I would do, but without LVM.
There were tools in Windows that could move partitions around, but I'm unsure in Linux. I think there was one, but I never tried. It is possible to grow a partition, at the end of it.
The only possibility without moving things is to add a /usr or /usr/something partition. And I would not do that. I would go the backup, repartition, restore route.
You can only shrink an ntfs gpt partition using windows 7 and up. Your idea of copying /usr to the new partition and mounting it separately sounds good. Shrinking a windows partition in windows is easy even in virtual box with reduced ram. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-02 12:27, Dave Plater wrote:
On 02/03/18 13:12, Carlos E. R. wrote:
On 2018-03-02 11:22, Dave Plater wrote:
In your case you will have to use LVM to add the gained space to your root partition, this I've no experience of but I think you can use yast.
This is far from trivial. Needs backup, repartition, format, recover from backup, reinstall grub.
Which is, anyway, what I would do, but without LVM.
There were tools in Windows that could move partitions around, but I'm unsure in Linux. I think there was one, but I never tried. It is possible to grow a partition, at the end of it.
The only possibility without moving things is to add a /usr or /usr/something partition. And I would not do that. I would go the backup, repartition, restore route.
You can only shrink an ntfs gpt partition using windows 7 and up. Your idea of copying /usr to the new partition and mounting it separately sounds good.
Except that /usr currently is huge, bigger than /. I would try to find a directory or several inside /usr that add up to the available space in the new partition. But then, you end having two roots and two /usr/something partitions, all needing free space, wasted, in a disk that is already smallish by current standards... Not optimal.
Shrinking a windows partition in windows is easy even in virtual box with reduced ram.
When it works :-) If there is an inmutable file in the middle, you can't. Happened to me... In that case, the DVD installer might shrink it. Me, I reinstalled Windows from the recovery partition on the laptop, booted it, and before allowing any update (no internet) shrinked it. Now that I think: George, find out where the space is actually used in your "/", maybe there are things you can delete, like a huge log file or /tmp. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/02/2018 07:55 PM, Carlos E. R. wrote:
On 2018-03-02 12:27, Dave Plater wrote:
Now that I think: George, find out where the space is actually used in your "/", maybe there are things you can delete, like a huge log file or /tmp.
Ok, after looking, I found out that the 2 biggest culprits are the journal file and the extra kernels. So I set the journal configuration file to a 100M limit, and that should help. Since I use the kernel:stable repository, I get frequent kernel updates, like around every 2 weeks. Some kernel files are stored in /lib/modules. The kernel source modules are stored in /usr/src. I don't know where other kernel files may be stored. I have kernel-default, kernel-devel, kernel-source, and kernel-syms installed. Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space. I think this will be a lot easier than messing with all the partitions, if I can just make a setting change. Then my 22.5G size should be plenty big for what I need. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* George from the tribe <tech@reachthetribes.org> [03-02-18 08:46]:
On 03/02/2018 07:55 PM, Carlos E. R. wrote:
On 2018-03-02 12:27, Dave Plater wrote:
Now that I think: George, find out where the space is actually used in your "/", maybe there are things you can delete, like a huge log file or /tmp.
Ok, after looking, I found out that the 2 biggest culprits are the journal file and the extra kernels.
So I set the journal configuration file to a 100M limit, and that should help.
Since I use the kernel:stable repository, I get frequent kernel updates, like around every 2 weeks.
Some kernel files are stored in /lib/modules. The kernel source modules are stored in /usr/src. I don't know where other kernel files may be stored. I have kernel-default, kernel-devel, kernel-source, and kernel-syms installed.
Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space. I think this will be a lot easier than messing with all the partitions, if I can just make a setting change. Then my 22.5G size should be plenty big for what I need.
if you are using zypper, look at /etc/zypp/zypp.conf and adjust multiversion.XXX to your preference. if yast, I cannot help. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-02 14:49, Patrick Shanahan wrote:
if you are using zypper, look at /etc/zypp/zypp.conf and adjust multiversion.XXX to your preference.
if yast, I cannot help.
It does not matter. It is a service which does the pruning, not zypper nor yast. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-03-02 14:43, George from the tribe wrote:
On 03/02/2018 07:55 PM, Carlos E. R. wrote:
On 2018-03-02 12:27, Dave Plater wrote:
Now that I think: George, find out where the space is actually used in your "/", maybe there are things you can delete, like a huge log file or /tmp.
Ok, after looking, I found out that the 2 biggest culprits are the journal file and the extra kernels.
So I set the journal configuration file to a 100M limit, and that should help.
Since I use the kernel:stable repository, I get frequent kernel updates, like around every 2 weeks.
Some kernel files are stored in /lib/modules. The kernel source modules are stored in /usr/src. I don't know where other kernel files may be stored. I have kernel-default, kernel-devel, kernel-source, and kernel-syms installed.
Are you sure you need the kernel sources? They are big.
Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space. I think this will be a lot easier than messing with all the partitions, if I can just make a setting change. Then my 22.5G size should be plenty big for what I need.
Yes, there is a setting. /etc/zypp/zypp.conf: multiversion.kernels = latest,latest-1,running That should normally mean 2 kernels. There is a service that applies this policy: systemctl status purge-kernels.service But to work it needs the kernel matching certain patterns. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 02/03/18 08:43 AM, George from the tribe wrote:
Some kernel files are stored in /lib/modules. The kernel source modules are stored in /usr/src. I don't know where other kernel files may be stored. I have kernel-default, kernel-devel, kernel-source, and kernel-syms installed.
Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space.
DON'T DO THAT ! ! ! It messes up grub, boot menus and stuff. Do it properly to maintain consistency: use 'purge-kennels' -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/02/2018 11:47 PM, Anton Aylward wrote:
On 02/03/18 08:43 AM, George from the tribe wrote:
Some kernel files are stored in /lib/modules. The kernel source modules are stored in /usr/src. I don't know where other kernel files may be stored. I have kernel-default, kernel-devel, kernel-source, and kernel-syms installed.
Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space.
DON'T DO THAT ! ! !
It messes up grub, boot menus and stuff.
Do it properly to maintain consistency: use 'purge-kennels'
Boy you were right about that. I have started using the 'purge-kernels' service now. Thanks to everyone for your advice on this. In trying to run purge-kernels, it kept failing on account of the different files I had deleted, making the system search for kernel files that weren't there. I then used zypper rm to get rid of the remaining older files that were listed in the purge-kernels status in order to finally get purge-kernels to start running. Oh, also, I had to create a file (I found an old thread that told how to do this) to make purge-kernels start working also. The status of the purge-kernels service kept saying that /boot/do_purge_kernels did not exist, so I had to run touch /boot/do_purge_kernels multiple times with each attempt to start the purge-kernels service, removing the rpms that were unnecessary using zypper, and finally it seems to have worked. I now have only 2 kernels installed: george@tribetrekDell:~> rpm -qa 'kernel*' | sort kernel-default-4.15.5-1.1.g52ce732.x86_64 kernel-default-4.15.7-1.1.ga36e160.x86_64 kernel-devel-4.15.5-1.1.g52ce732.noarch kernel-devel-4.15.7-1.1.ga36e160.noarch kernel-firmware-20180201-35.1.noarch kernel-macros-4.15.7-1.1.ga36e160.noarch kernel-source-4.15.5-1.1.g52ce732.noarch kernel-source-4.15.7-1.1.ga36e160.noarch And look, my disk use is freed up (thankfully!) george@tribetrekDell:~> df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 8.0K 3.9G 1% /dev tmpfs 3.9G 15M 3.9G 1% /dev/shm tmpfs 3.9G 2.5M 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda6 22G 17G 4.1G 81% / /dev/sda1 196M 29M 168M 15% /boot/efi /dev/sda8 327G 306G 3.8G 99% /home /dev/sda3 64G 43G 21G 67% /windows/C tmpfs 785M 28K 785M 1% /run/user/1000 There was an old bug about the specific file not being created when trying to run purge-kernels, but I don't know if my problem might have been created on the system upgrade, rather than through the bug. I will watch and see if this happens again. One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-03 10:55, George from the tribe wrote:
Oh, also, I had to create a file (I found an old thread that told how to do this) to make purge-kernels start working also. The status of the purge-kernels service kept saying that /boot/do_purge_kernels did not exist, so I had to run
touch /boot/do_purge_kernels
multiple times with each attempt to start the purge-kernels service, removing the rpms that were unnecessary using zypper, and finally it seems to have worked.
You also have to verify that the service is "enabled": systemctl status purge-kernels.service so that it runs automatically when it should.
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/03/18 11:47, Carlos E. R. wrote:
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd".
Does it really matter if unnecessary kernels are listed in grub? Next time there's a kernel upgrade, SUSE should regenerate the automated list and get rid of them. Look at where it says "autogenerated by SUSE" or whatever in grub.cfg. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-03 13:07, Wol's lists wrote:
On 03/03/18 11:47, Carlos E. R. wrote:
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd".
Does it really matter if unnecessary kernels are listed in grub? Next time there's a kernel upgrade, SUSE should regenerate the automated list and get rid of them.
Correct, but it gets confusing if you want to boot the non-default one. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/03/18 07:24 AM, Carlos E. R. wrote:
On 2018-03-03 13:07, Wol's lists wrote:
On 03/03/18 11:47, Carlos E. R. wrote:
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd".
Does it really matter if unnecessary kernels are listed in grub? Next time there's a kernel upgrade, SUSE should regenerate the automated list and get rid of them.
Correct, but it gets confusing if you want to boot the non-default one.
What's confusing? So long as you've done things cleanly/properly and not gone around using 'rm' on your kernels or modules, then the grub menu should reflect the kernels you have available. When my grub menu comes up there is the default, the current kernel, and if I do nothing then timeout will activate that, but I can seelct the menu entry below it and go to the secondary menu and see all my older kernels. What's confusing about that? If you muck around manually, then yes, things can easily become inconsistent, get out of sync with each other and get confused, confuse the user and result in confused reporting of the problem and don't expect me to solve it by remote consulting via email. Arbitrarily manually deleting stuff is a good way to create inconsistencies. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-03 13:51, Anton Aylward wrote:
On 03/03/18 07:24 AM, Carlos E. R. wrote:
On 2018-03-03 13:07, Wol's lists wrote:
On 03/03/18 11:47, Carlos E. R. wrote:
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd".
Does it really matter if unnecessary kernels are listed in grub? Next time there's a kernel upgrade, SUSE should regenerate the automated list and get rid of them.
Correct, but it gets confusing if you want to boot the non-default one.
What's confusing? So long as you've done things cleanly/properly and not gone around using 'rm' on your kernels or modules, then the grub menu should reflect the kernels you have available.
The assumption is "you've *not* done things cleanly/properly" and "unnecessary kernels are listed in grub". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/03/18 08:19 AM, Carlos E. R. wrote:
The assumption is "you've *not* done things cleanly/properly" and "unnecessary kernels are listed in grub".
I wouldn't say "unnecessary", I'd say 'non existent' or 'incomplete'. If someone had manually deleted a kernel from /boot or a set of modules from /lib then it is inconsistency that is the issue. That's why I say DON'T DO THAT. Using 'purge-kernels' is the high level way of dealing with it. Yes you can do the 'zypper rm <old kernel package>' or even the 'rpm -e <old kernel package>', that eventually 'purge-kernels' uses, but why? The higher level tool does consistency checks and deals with sources and a more. Yes the 'more' may or may not apply in your case, but ... there's some reasons and ... well go see the source of 'purge-kernels'. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/2018 11:45 PM, Anton Aylward wrote:
On 03/03/18 08:19 AM, Carlos E. R. wrote:
The assumption is "you've *not* done things cleanly/properly" and "unnecessary kernels are listed in grub". I wouldn't say "unnecessary", I'd say 'non existent' or 'incomplete'. If someone had manually deleted a kernel from /boot or a set of modules from /lib then it is inconsistency that is the issue.
That's why I say DON'T DO THAT.
Using 'purge-kernels' is the high level way of dealing with it. Yes you can do the 'zypper rm <old kernel package>' or even the 'rpm -e <old kernel package>', that eventually 'purge-kernels' uses, but why? The higher level tool does consistency checks and deals with sources and a more. Yes the 'more' may or may not apply in your case, but ... there's some reasons and ... well go see the source of 'purge-kernels'.
Yes in my case because I was unaware of the purge-kernels service before this started, and the fault happened right in the middle of the upgrade. One module of a new kernel had been installed, but the other modules would not install, because there was no room on the drive. I had searched for where the partition was filling up, and not knowing what else to do at the time, had removed some modules of old kernels. So then when I started to use the purge-kernels service, after people here made me aware of it. I found that the reason it was failing to start was because of the things I had done earlier - removing some kernel modules manually, but not removing others. So by that point, the only way to get purge-kernels to work at all was to try and start it, look at what was causing it to fail (incomplete kernel installations), manually delete those incomplete pieces, and try running it again. I think I had about 4 incomplete kernel installations that I had to manually delete, but another 4 that were complete. So once I had manually removed all the incomplete installations, I was able to finally run purge-kernels and make it work. Then it looked through my system and found the other old kernel installations, which were complete but un-necessary, and deleted them the proper way. So my system is much cleaner now. Again, thanks to everyone for helping me figure this out. I am still thinking about future re-partitioning of my SSD so there is more room in the root, but haven't decided yet what to do. In the meantime, I am glad I at least have room on my drive to work and run updates now. -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I don't think so, but if worried, run "mkinitrd".
Does it really matter if unnecessary kernels are listed in grub? Next time there's a kernel upgrade, SUSE should regenerate the automated list and get rid of them.
kernel packages update bootloader configuration on install and remove. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/18 06:47 AM, Carlos E. R. wrote:
n 2018-03-03 10:55, George from the tribe wrote:
Oh, also, I had to create a file (I found an old thread that told how to do this) to make purge-kernels start working also. The status of the purge-kernels service kept saying that /boot/do_purge_kernels did not exist, so I had to run
touch /boot/do_purge_kernels
multiple times with each attempt to start the purge-kernels service, removing the rpms that were unnecessary using zypper, and finally it seems to have worked. You also have to verify that the service is "enabled":
systemctl status purge-kernels.service
so that it runs automatically when it should.
IF AND ONLY IF you want it to run automatically. I don't. I'm not saying you shouldn't for any particular "you", just that there may be reasons you want to have more control over the deletion of old kernels for a variety of reasons. Maybe you have a FS on a USB stick that was created with an older version of the FS. I hit this with XFS once. Maybe you want to keep the kernel that came with the distribution and haven't figured out how to do that in zypp.conf. Maybe a lot of things and want manual control. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/18 04:55 AM, George from the tribe wrote:
One more question - I assume I should probably reinstall grub now that the kernels are purged? Or is that included as something that the purge-kernels service does automatically? It did not show any output indicating anything to that effect on the command line when I ran it.
I'm not sure what you mean by "reinstall grub". if you mean "zypper install grub" then I don't see any reason. If you mean do you remake the grub.conf to reflect in the boot menu what kernels you do not have, then that is done automagically by the purge_kernels. /sbin/purge-kernels is a Perl script and as such readable with a text browser. Even if you can't program in Perl, you should be able to understand the flow of logic and the calling of library and system functions and externals. You can find out a LOT about how the system work by using 'apropos' to find man pages on a subject, and file $(which <program-name>) Even if it is a binary, you can use 'ldd' to see what libraries get used which can be highly clueful, and if skilled enough you can trace execution to see what actual system calls are made, for example, to various (and possibly unexpected!) config files, or if the program makes queries over the net or gives away your credentials to a remote site. It may sound deep for a beginner, but there are many HOW-TO articles on the net, books on same, and it is very logical and procedural. Don't be scared off from taking a look and learning. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, March 3, 2018 4:55:26 AM EST George from the tribe wrote:
Is there somewhere that I can tell my system to only keep 3 kernels? There were like 6 old kernels in those locations. I went and manually deleted the old ones and it freed up some space.
George, fyi, the "multiversion" switch in /etc/zypp.conf can control this. The following will instruct zypper/yast to always keep the current and previous 2 kernels: multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,latest-2,running Setting this and reinstalling the recent kernel would have purged your old kernels plus all the files you unintentionally stranded plus regenerated grub. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/18 04:32 AM, George from the tribe wrote:
Is that something that is even possible?
There are a lot of possibilities. Do read this to start: https://www.ibm.com/developerworks/library/l-resizing-partitions-1/ <quote> Partition resizing is inherently at least a little bit risky. Partition resizing software must alter low-level partition and file system data structures and possibly move significant amounts of data. Problems such as corrupt data on the disk, power failures, and system crashes can all cause catastrophic failure of the resizing process. For this reason, you should not undertake a partition resizing operation lightly, and, whenever possible, you should back up your data, as described in "Preparing a backup." </quote> Consider also that you may need to run the partitioner "off line", that is from the recovery DVD or from a "LiveCD".
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
Yes, you *can* but I wouldn't. It gets confusing come maintenance, and/or updates. if you do this, make sure that you document it. I'd use red ink. I really really really really REALLY hate pre-provisioning with a vengeance. I can't emphasise this too strongly. This approach to partitioning is a classic example of pre-provisioning. Ext4 is another example of pre-provisioning that I regularly rant against. That being said, paritioners have got smart over the years. See above. Once upon a time it took a tool called "Partition Magic" to shuffle partitions around in the way you are asking for, shrinking and growing file systems under the partitions in ways that the original FS designers never envisioned possible. Now we have file systems that can be grown if you can grow the partition. Check the man pages or Wikipedia. https://en.wikipedia.org/wiki/Comparison_of_file_systems#Resize_capabilities You can certainly grow an ext4FS, on-line or off-line. Again, check the man pages. You can't shrink one easily. back to the "smart" partitioner. As you can see, the Windows FAT file systems are not size-change friendly, but the NTFS is. Once upon a time after I'd moved my life to Linux I tried using the partitioner to shrink the Windows/FAT partition to make room for the Linux. I lost everything. I hope the partitioner tools have improved, but I'd still recommend making a complete backup. After that disaster I decided I really didn't need Windows on that machine. The one-and-only-one application I needed Windows for I could run on an older, lesser machine, when I needed to. I've never looked back. I've also never had to play repartitioning games because I also adopted LVM. This was more in my fight against pre-partitioning. I'd been using a similar tool under IBM's AIX on a an multi-processor cluster. That lets me shrink or grow a 'logical partition' on a live machine with the FS in use, or even extend the LP across drives or move to another drive. All the things you can do with BtrFS but this works with ANY file system. Of course if you do shrink of grow the LP you'll need a FS that shrinks and grows, too. That's why I chose to use ReiserFS. Not only is it a REAL B-Tree FS in that it has no pre-provisioning with a hard boundary between the number of i-nodes and the amount of data space, an archaic concept that goes back to the early 1970s and the old, slow, original UNIX v6/V7 file systems, but one that we can still see in ext4, but it can both shrink and grow on a life system. Other real B-tree file systems for Linux include, apart from BtrFS, XFS, JFS, and in due course, I hope, Reiser4FS. https://stackoverflow.com/questions/32512700/why-b-tree-for-file-systems The Linux JFS hasn't yet caught up with the version of JFS2 on AIX that I (occasionally) use in that it doesn't support both on-line grow and shrink. The Linux version I have to take off-line to grow. If you're happy with Ext4 and can put up with the pre-provisioning then OK. But even right now you might be facing a exhaustion of the data space in your root partition while there is plenty of inode space available. For example, on one of the few Ext4 file systems I have ... # df /usr/local Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vgmain-vLOCAL 3030800 1603412 1253720 57% /usr/local main:~ # df -i /usr/local Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/vgmain-vLOCAL 196608 11121 185487 6% /usr/local See: 57% of data space used but only 6% of inode space used. So I might get to the point were about 98% of the data space is used but only about 10% of the i-node space. Check your own system. That's why I prefer to use a REAL b-tree FS like JFS or XFS or ReiserFS. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-03-02 12:22, Anton Aylward wrote:
On 02/03/18 04:32 AM, George from the tribe wrote:
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
Yes, you *can* but I wouldn't. It gets confusing come maintenance, and/or updates. if you do this, make sure that you document it. I'd use red ink.
It also means having two partitions with empty, spare, space. In this case, four. Not a good thing with a smallish disk. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 02/03/18 04:32 AM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
Do you really need Windows on that machine? Do you really need that much Windows space on that machine? Do you really need both root partitions? There's a lot that gets put in some root layouts that could be shared, stuff under /usr/share for example that was intended to be shared like the man pages. Do you really need all those extra language files? I use a utility called 'bleachbit' to clean up old files and that includes language files I don't need. It can also purge old logs and more. I've cleaned about 500Meg worth, nearly 20,000 files of language and old logs off my system after my last 'update'. I could have cleaned more with more aggressive settings. https://www.howtogeek.com/116971/7-tips-to-get-the-most-out-of-bleachbit-a-c... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/02/2018 07:40 PM, Anton Aylward wrote:
On 02/03/18 04:32 AM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
Do you really need Windows on that machine? Yes, unfortunately. I rarely use it, but every once in a while something really important comes up that requires it.
Do you really need that much Windows space on that machine? Certainly not. I could shrink about 14G off of it and use that as a spare partition.
Do you really need both root partitions? There's a lot that gets put in some root layouts that could be shared, stuff under /usr/share for example that was intended to be shared like the man pages. It really has been nice to have this feature, as I have messed up installations before, and then I had a sudden need to get back on my pc with no time to spare to repair the botched install. So yes, having 2 root partitions is probably very important.
However, what you are suggesting is very intriguing. My share folder is about 4G. Perhaps I could move this to the extra space, if I decide to shrink the windows partition as noted above.
Do you really need all those extra language files? I use a utility called 'bleachbit' to clean up old files and that includes language files I don't need. It can also purge old logs and more. I've cleaned about 500Meg worth, nearly 20,000 files of language and old logs off my system after my last 'update'. I could have cleaned more with more aggressive settings.
https://www.howtogeek.com/116971/7-tips-to-get-the-most-out-of-bleachbit-a-c...
I will definitely look into bleachbit. In the meantime, where are all the language files kept? I know I don't need all those language files. English is the only language I need documentation for. Is there a setting that can specify only English, or English and Spanish, so that all those language files can be deleted? -- George Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.3 | Gnome 3.20 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 42.3 | Gnome 3.20 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/18 09:26 AM, George from the tribe wrote:
On 03/02/2018 07:40 PM, Anton Aylward wrote:
On 02/03/18 04:32 AM, George from the tribe wrote:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
Do you really need Windows on that machine? Yes, unfortunately. I rarely use it, but every once in a while something really important comes up that requires it.
I had that situation. The 'rarely' stretched out and out and I scrounged an old machine and put Windows on that for when I did need it and freed up space on my my (then) laptop.
Do you really need that much Windows space on that machine? Certainly not. I could shrink about 14G off of it and use that as a spare partition.
Well, free it, yes, but don't think of another partition. Use the partitioner to grow what you have. Ext4FS can be made to grow once ytou have grown the partition it resides in.
Do you really need both root partitions? There's a lot that gets put in some root layouts that could be shared, stuff under /usr/share for example that was intended to be shared like the man pages. It really has been nice to have this feature, as I have messed up installations before, and then I had a sudden need to get back on my pc with no time to spare to repair the botched install. So yes, having 2 root partitions is probably very important.
I can understand two minimalist versions, but there is a lot you can strip out and put in common. it's one reason I have so many partitions. It also means that those other partitions, not just home, but things like /usr/local, my web stuff in /srv and more, that are all independent of the OS itself, can survive an upgrade that wipes the OS partition. Now THAT is an area where putting them all in another partition and using symlinks or bind-mount makes sense.
However, what you are suggesting is very intriguing. My share folder is about 4G. Perhaps I could move this to the extra space, if I decide to shrink the windows partition as noted above.
Do you really need all those extra language files? I use a utility called 'bleachbit' to clean up old files and that includes language files I don't need. It can also purge old logs and more. I've cleaned about 500Meg worth, nearly 20,000 files of language and old logs off my system after my last 'update'. I could have cleaned more with more aggressive settings.
https://www.howtogeek.com/116971/7-tips-to-get-the-most-out-of-bleachbit-a-c...
I will definitely look into bleachbit. In the meantime, where are all the language files kept? I know I don't need all those language files. English is the only language I need documentation for. Is there a setting that can specify only English, or English and Spanish, so that all those language files can be deleted?
Yes, bleachbit can be configured in many details, and which languages to keep is one of them. The answer to the 'where' is "many places". Which is why I use bleachbit. In any case, you can use bleachbit in non-commit mode and it will list what it would do, so you can find out the locations that way. I do know a bunch of them are under /usr/share/locale/ but there are a lot more. Some seem to be application specific :-( However if you were to, as I suggested, factor out the /usr/share, in part or in all, and really share it, then you're more than halfway there. Oh, right, Richard Brown has things to say about that. Check the archives for his comments about that, and about having a separate /boot. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2 Mar 2018 17:32:47 +0800 George from the tribe <tech@reachthetribes.org> wrote:
I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive,
That's fine and fairly east.
split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room.
That sounds very hard and complex -- and unnecessary. What version of Windows? Step 1, clean it up. Windows keeps a lot of junk around. You can do this from Linux -- look for /Windows/Temp and delete everything in it. Then look for /Users/$username/Application Data/Local/Temp (for all users) and delete everything in there too. Then boot into Windows. Run the System Cleanup tool. Tick all the boxes, let it clean. Run it again. Press "clean up system files". Tick all the boxes, let it clean. Empty the trash. In a terminal with admin permissions, type: chkdsk c: /f Reboot and let it run. Then you should be able to use Disk Management (Start | Run | diskmgmt.msc) to shrink the C partition. If it will shrink it as much as you want, great. If not, do as much as it can. Now boot into Linux again. Delete any pagefiles/swapfiles from your Windows drive. Now, make a Live medium and boot from that. Using GParted: [1] shrink the Windows partition as much as you want. [2] Move your first root partition up into the space you've freed up. [3] Count how much free space there is. Halve this number: call it x GB. [4] Enlarge root partition #1 by x GB. [3] Move root partition #2 to right after root partition #1. [4] Enlarge root partition #2 by x GB. That's it. Reboot the box. You should now have both root partitions bigger by about 50% of how much space you took off the root partition. No need for LVM or anything scary like that. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Forget it, your Windows partition is already minimal -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 2 maart 2018 10:32:47 CET schreef George from the tribe:
I am on working on my laptop (#2 below, a dell XPS). It has a 500gb SSD which is partitioned for dual boot windows and opensuse.
My root partition is almost completely full, and I am wondering what I can do about it to make more space.
Here is the layout of the drive:
tribetrekDell:/ # fdisk -l Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2C1BF30F-7D76-4D8E-A2CB-FD86115234B3
Device Start End Sectors Size Type /dev/sda1 2048 411647 409600 200M EFI System /dev/sda2 411648 444415 32768 16M Microsoft reserved /dev/sda3 444416 133564415 133120000 63.5G Microsoft basic data /dev/sda4 935960576 937701375 1740800 850M Windows recovery environment /dev/sda5 133564416 146245631 12681216 6G Linux swap /dev/sda6 146245632 193349631 47104000 22.5G Linux filesystem /dev/sda7 193349632 240453631 47104000 22.5G Linux filesystem /dev/sda8 240453632 935960575 695506944 331.7G Linux filesystem
Partition table entries are not in disk order.
I have 2 root drives, both 22.5G, for the purpose of when the time comes to upgrade, having the previous version backed up in order to be able to boot into my system if the upgrade fails, or I have some other kind of major failure. It has saved my back many times.
So, I want to keep the 22.5G drives equally sized, and I don't want to reduce the "home" partition of 331.7G.
I noticed that /dev/sda3 for windows is only using about 45G on it. Since I hardly ever use windows, I was thinking of trying to take 14G off of that drive, split it into 2 partitions, and somehow append those extra 7G to each of the root drives in order to give my root more room.
Is that something that is even possible?
Does anyone have better recommendations? Like splitting off some of the directories from my root drive that take up a lot of memory, and moving them to the new partitions, and then just symlinking to those partitions in order to continue running?
I don't really know the best course of action here. Any help is greatly appreciated. Re. the kernels: have a look at this line in /etc/zypp/zypp.conf multiversion.kernel = ....
This value determines how many previous kernelpackages-versions will be kept. In your case the sources will be the culprit. Have a look at rpm -qa | grep kernel-source You could remove older sources by zypper rm "FULL_PACKAGE_NAME_HERE". -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (13)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Dave Plater -
Dennis Gallien -
George from the tribe -
Jdd -
Knurpht - Gertjan Lettink -
Liam Proven -
Patrick Shanahan -
Peter Suetterlin -
Wol's lists -
Wols Lists