[opensuse-factory] Question on partition manager in 15.1 alfa (did not try on beta yet)
have a partition with /boot / /home /swap on a 30 GB partition in KVM Now the 30 GB were a limitation of a former disc. So I have space now to copy for testing real home. I resized the disc space available and then I did boot the VM. It showed obviously 300 GB available and unpartitioned after the /swap. So I wanted to use these plus of 300 GB for home. I did erase the swap. I then tried to upsize home and it would offer only all space available. But I wanted to to have the swap in front of home. So I did create on the free space an ext4 partition with home, mounted it as newhome and rsynced home. At the end umount /home and I mounted the newhome now as home. now I did restart and then I went to partition manager. there was the free 30 GB in the middle between root and home. So I created first 2 GB Swap. Good, no problem. Now I wanted to either shift and then upsize home or to extend home right away to use the available disc space (not partitioned). But the partitioner said: No free space available. So he does not see uphill disk space? So I tried to move the partition. But this is apparently not possible because already created on the disc. I understand the latter but is it normal that a resizing is not possible? Is this a known shortcoming of partitioning or is it a problem of the 15.1 partitioner? (Be patient with my ignorance). _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
Now the 30 GB were a limitation of a former disc. So I have space now to copy for testing real home. I resized the disc space available and then I did boot the VM. It showed obviously 300 GB available and unpartitioned after the /swap. So I wanted to use these plus of 300 GB for home. I did erase the swap. I then tried to upsize home and it would offer only all space available. But I wanted to to have the swap in front of home. So I did create on the free space an ext4 partition with home, mounted it as newhome and rsynced home. At the end umount /home and I mounted the newhome now as home. now I did restart and then I went to partition manager. there was the free 30 GB in the middle between root and home. So I created first 2 GB Swap. Good, no problem. Now I wanted to either shift and then upsize home or to extend home right away to use the available disc space (not partitioned). But the partitioner said: No free space available. So he does not see uphill disk space? So I tried to move the partition. But this is apparently not possible because already created on the disc. I understand the latter but is it normal that a resizing is not possible? Is this a known shortcoming of partitioning or is it a problem of the 15.1 partitioner? (Be patient with my ignorance).
The default partitioners in the distros have relatively little power, and are designed to do the ordinary kinds of things that worked for you, and to avoid dangerous operations such as moving a partition, which is very dangerous for the data in that partition. The things you want to do are best done with GParted. My suggestion is that you download the live GParted iso, boot that and do the things that you want. Doing a live version avoids problems with trying to do things on a mounted volume. Since you are working with a VM, you won't even need to burn a CD. I also suggest that you make another copy of the data in /home before you try to move that partition. I once lost the entire contents of a disk because there was a power glitch while I was moving a partition. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
Now the 30 GB were a limitation of a former disc. So I have space now to copy for testing real home. I resized the disc space available and then I did boot the VM. It showed obviously 300 GB available and unpartitioned after the /swap. So I wanted to use these plus of 300 GB for home. I did erase the swap. I then tried to upsize home and it would offer only all space available. But I wanted to to have the swap in front of home. So I did create on the free space an ext4 partition with home, mounted it as newhome and rsynced home. At the end umount /home and I mounted the newhome now as home. now I did restart and then I went to partition manager. there was the free 30 GB in the middle between root and home. So I created first 2 GB Swap. Good, no problem. Now I wanted to either shift and then upsize home or to extend home right away to use the available disc space (not partitioned). But the partitioner said: No free space available. So he does not see uphill disk space? So I tried to move the partition. But this is apparently not possible because already created on the disc. I understand the latter but is it normal that a resizing is not possible? Is this a known shortcoming of partitioning or is it a problem of the 15.1 partitioner? (Be patient with my ignorance).
The default partitioners in the distros have relatively little power, and are designed to do the ordinary kinds of things that worked for you, and to avoid dangerous operations such as moving a partition, which is very dangerous for the data in that partition. The things you want to do are best done with GParted. My suggestion is that you download the live GParted iso, boot that and do the things that you want. Doing a live version avoids problems with trying to do things on a mounted volume. Since you are working with a VM, you won't even need to burn a CD.
I also suggest that you make another copy of the data in /home before you try to move that partition. I once lost the entire contents of a disk because there was a power glitch while I was moving a partition.
Larry Thanks. For what it is good for: the installation is for testing purposes and to see if migrated my laptop and files will perform as desired. The question was more to understand if this is a bug to be reported or not. It seems it is not. Currently I am still trying to a) import an archive of kmail into the new account with postgres10. If I succeed I will try to upgrade another similar account from 9.6 to 10. All for learning purposes, so you see, I have a lot of
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto: things to do. Thank you for the heads up. Regards. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>) escribió:
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
Now the 30 GB were a limitation of a former disc. So I have space now to copy for testing real home. I resized the disc space available and then I did boot the VM. It showed obviously 300 GB available and unpartitioned after the /swap. So I wanted to use these plus of 300 GB for home. I did erase the swap. I then tried to upsize home and it would offer only all space available. But I wanted to to have the swap in front of home. So I did create on the free space an ext4 partition with home, mounted it as newhome and rsynced home. At the end umount /home and I mounted the newhome now as home. now I did restart and then I went to partition manager. there was the free 30 GB in the middle between root and home. So I created first 2 GB Swap. Good, no problem. Now I wanted to either shift and then upsize home or to extend home right away to use the available disc space (not partitioned). But the partitioner said: No free space available. So he does not see uphill disk space? So I tried to move the partition. But this is apparently not possible because already created on the disc. I understand the latter but is it normal that a resizing is not possible? Is this a known shortcoming of partitioning or is it a problem of the 15.1 partitioner? (Be patient with my ignorance).
The default partitioners in the distros have relatively little power, and are designed to do the ordinary kinds of things that worked for you, and to avoid dangerous operations such as moving a partition, which is very dangerous for the data in that partition. The things you want to do are best done with GParted. My suggestion is that you download the live GParted iso, boot that and do the things that you want. Doing a live version avoids problems with trying to do things on a mounted volume. Since you are working with a VM, you won't even need to burn a CD.
I also suggest that you make another copy of the data in /home before you try to move that partition. I once lost the entire contents of a disk because there was a power glitch while I was moving a partition.
Larry Thanks. For what it is good for: the installation is for testing purposes and to see if migrated my laptop and files will perform as desired. The question was more to understand if this is a bug to be reported or not. It seems it is not. Currently I am still trying to a) import an archive of kmail into the new account with postgres10. If I succeed I will try to upgrade another similar account from 9.6 to 10. All for learning purposes, so you see, I have a lot of
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto: things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information Cheers, Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>) escribió:
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto:
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
SNIP (for clearness) for learning purposes, so you see, I have a
lot of things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information
Cheers, Juan Oh, yes, that was the issue with 15.0 (before it was fixed). It is fixed now BTW (but only when you activate the internet and repos prior installation. I will test this by doing a clone and try an update on 15.0 to 15.1. An advice (especially with friends - I KNOW the issue of data loss really). always backup the day before, ideally hours before the installation all /home when you do an upgrade / new install. It is worth it. (On the false line of
In data venerdì 22 febbraio 2019 13:02:19 CET, hai scritto: the song of Alanis Morrisett "Isn't it ironic". ;-) : giving you the advice that you just didn't take. Thanks for reminding me. Regards. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/22/19 1:28 PM, stakanov wrote:
In data venerdì 22 febbraio 2019 13:02:19 CET, hai scritto:
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>) escribió:
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto:
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
SNIP (for clearness) for learning purposes, so you see, I have a
lot of things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information
Cheers, Juan Oh, yes, that was the issue with 15.0 (before it was fixed). It is fixed now BTW (but only when you activate the internet and repos prior installation.> I will test this by doing a clone and try an update on 15.0 to 15.1. An advice (especially with friends - I KNOW the issue of data loss really).
Can you please point to the exact bug report and/for fix you are referring to? I have followed quite closely the partitioner-related development of 15.0 and 15.1. There has been indeed quite some bugs in that area and many of them has been fixed with online maintenance updates, as you pointed. But I'm not aware about none of those bugs being: "YaST deletes a partition it has not been told to delete or that was not explicitly mentioned in the proposal to be deleted". Thanks. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/22/19 1:28 PM, stakanov wrote:
In data venerdì 22 febbraio 2019 13:02:19 CET, hai scritto:
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>)
escribió:
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto:
On 2/21/19 9:12 AM, stakanov wrote:
have a partition with /boot / /home /swap
on a 30 GB partition in KVM
SNIP (for clearness)
for learning purposes, so you see, I have a
lot of things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information
Cheers,
Juan
Oh, yes, that was the issue with 15.0 (before it was fixed). It is fixed now BTW (but only when you activate the internet and repos prior installation.> I will test this by doing a clone and try an update on 15.0 to 15.1. An advice (especially with friends - I KNOW the issue of data loss really). Can you please point to the exact bug report and/for fix you are referring to?
I have followed quite closely the partitioner-related development of 15.0 and 15.1. There has been indeed quite some bugs in that area and many of them has been fixed with online maintenance updates, as you pointed.
But I'm not aware about none of those bugs being: "YaST deletes a partition it has not been told to delete or that was not explicitly mentioned in the proposal to be deleted".
Thanks. The bug was as follows: if, during installation of a 15.1, you choose not to update (as many users do because of issues or because they want a fresh system) they do the following: use the existing partitions and and then read in the users with the help of "expert partition manager". In this routine the "expert partition manager" would be so kind that it selected the /home (especially if you have e.g. on an LVM but not only) and did put it to format. You could (if distrustful enough and very attentive) see it and deny the
In data venerdì 22 febbraio 2019 13:59:04 CET, hai scritto: formatting. Then all went well. The bug (so far I have seen in 15) is now fixed (as it seems by an update done to the installer/yast, right after activating the repos). Bug number: I do not find it, maybe user Carlso E.R. (robin.listas) has reported it, I am not sure. the bug is still visible when you follow (without activating the network) the original install iso of opensuse 15. Setup: /boot (efi) LVM encrypted with / root (ext4) /swap (swap) /home (ext4) You give the password of the encrypted volume. You are proposed to install with btrfs. When you refuse the proposal, then you go to expert partitioner, then "read in existing installation". The program will read in all existing partitions, but now sets /home to be formatted, toghether with root and swap. I recall maybe it does not want to format /boot. But I am not sure. Repeatable always (with install from 42.3 as said to 15.0) doing a expert partitioning without network. Hope that helps. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
In data venerdì 22 febbraio 2019 21:22:14 CET, stakanov ha scritto:
The bug was as follows: if, during installation of a 15.1,
Sorry that wanted to be 15.0 _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 22/02/2019 21.22, stakanov wrote:
In data venerdì 22 febbraio 2019 13:59:04 CET, hai scritto:
On 2/22/19 1:28 PM, stakanov wrote:
The bug was as follows: if, during installation of a 15.1, you choose not to update (as many users do because of issues or because they want a fresh system) they do the following: use the existing partitions and and then read in the users with the help of "expert partition manager". In this routine the "expert partition manager" would be so kind that it selected the /home (especially if you have e.g. on an LVM but not only) and did put it to format. You could (if distrustful enough and very attentive) see it and deny the formatting. Then all went well. The bug (so far I have seen in 15) is now fixed (as it seems by an update done to the installer/yast, right after activating the repos). Bug number: I do not find it, maybe user Carlso E.R. (robin.listas) has reported it, I am not sure.
I remember the issue, but I'm unable so far to locate the report. As you describe it, it will be rejected it because the system did say it was going to format home. And I was told this is intentional behaviour. Maybe it was in the factory mail list at the time, not in a bugzilla. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2/22/19 9:22 PM, stakanov wrote:
On 2/22/19 1:28 PM, stakanov wrote:
In data venerdì 22 febbraio 2019 13:02:19 CET, hai scritto:
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>)
escribió:
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto:
On 2/21/19 9:12 AM, stakanov wrote: > have a partition with > /boot > / > /home > /swap > > on a 30 GB partition in KVM
SNIP (for clearness)
for learning purposes, so you see, I have a
lot of things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information
Cheers,
Juan
Oh, yes, that was the issue with 15.0 (before it was fixed). It is fixed now BTW (but only when you activate the internet and repos prior installation.> I will test this by doing a clone and try an update on 15.0 to 15.1. An advice (especially with friends - I KNOW the issue of data loss really). Can you please point to the exact bug report and/for fix you are referring to?
I have followed quite closely the partitioner-related development of 15.0 and 15.1. There has been indeed quite some bugs in that area and many of them has been fixed with online maintenance updates, as you pointed.
But I'm not aware about none of those bugs being: "YaST deletes a partition it has not been told to delete or that was not explicitly mentioned in the proposal to be deleted".
Thanks. The bug was as follows: if, during installation of a 15.1, you choose not to update (as many users do because of issues or because they want a fresh system) they do the following: use the existing partitions and and then read in the users with the help of "expert partition manager". In this routine the "expert partition manager" would be so kind that it selected the /home (especially if you have e.g. on an LVM but not only) and did put it to format. You could (if distrustful enough and very attentive) see it and deny the
In data venerdì 22 febbraio 2019 13:59:04 CET, hai scritto: formatting. Then all went well.
Ok! Now I got it! This bug is about using the "Import Mountpoints" button in the Expert Partitioner. But none you or Juan Erbes has mentioned such button in this thread or in the other one[*]. So I was completely lost. Now we have an starting point to discuss what was missing/broken in that particular button and what have been improved/fixed after 15.0. [*] I mean the already linked thread in which is stated that the installation didn't offer any partitioning-related screen and just deleted /home without even mentioning it. https://lists.opensuse.org/opensuse-factory/2018-11/msg00172.html
The bug (so far I have seen in 15) is now fixed (as it seems by an update done to the installer/yast, right after activating the repos). Bug number: I do not find it, maybe user Carlso E.R. (robin.listas) has reported it, I am not sure.
The bug was indeed reported (but not by any of the people taking part in the ML threads) and fixed AFTER the release of 15.0. See https://bugzilla.suse.com/show_bug.cgi?id=1094924
the bug is still visible when you follow (without activating the network) the original install iso of opensuse 15.
Yes, the "import mountpoints" in Leap 15.0 didn't have the checkbox titled "Format System Volumes". Instead, all imported mountpoints were marked for format. The checkbox was added after the 15.0 release, so you will only get it (together with the more conservative default behavior) if using 15.1, TW or 15.0+update_repos.
You give the password of the encrypted volume. You are proposed to install with btrfs. When you refuse the proposal, then you go to expert partitioner, then "read in existing installation". The program will read in all existing partitions, but now sets /home to be formatted, toghether with root and swap. I recall maybe it does not want to format /boot. But I am not sure. Repeatable always (with install from 42.3 as said to 15.0) doing a expert partitioning without network. Hope that helps.
Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
In data lunedì 25 febbraio 2019 12:53:51 CET, hai scritto:
On 2/22/19 9:22 PM, stakanov wrote:
In data venerdì 22 febbraio 2019 13:59:04 CET, hai scritto:
On 2/22/19 1:28 PM, stakanov wrote:
In data venerdì 22 febbraio 2019 13:02:19 CET, hai scritto:
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>)
escribió:
In data giovedì 21 febbraio 2019 18:02:37 CET, Larry Finger ha scritto: > On 2/21/19 9:12 AM, stakanov wrote:
Ok! Now I got it! This bug is about using the "Import Mountpoints" button in the Expert Partitioner.
But none you or Juan Erbes has mentioned such button in this thread or in the other one[*]. So I was completely lost.
The checkbox was added after the 15.0 release, so you will only get it (together with the more conservative default behavior) if using 15.1, TW or 15.0+update_repos.
You give the password of the encrypted volume. You are proposed to install with btrfs. When you refuse the proposal, then you go to expert partitioner, then "read in existing installation". The program will read in all existing partitions, but now sets /home to be formatted, toghether with root and swap. I recall maybe it does not want to format /boot. But I am not sure. Repeatable always (with install from 42.3 as said to 15.0) doing a expert partitioning without network. Hope that helps.
Cheers.
You have to pardon us, while installing quite some systems over the year, the frequency of it is not such, that I would recall it was a button. So have patience with the somewhat flurry indications. Good to know that it has been fixed (was a "wow!" experience, but I caught it before it happened :-p ). Thank you for informing us about it being officially fixed. Should anything arise with the partitioner in 15.1 beta, I will let you know in case. 15.1: excellent work, quite neat up to now, as it seems. Compliments to all the team working on it. Kind regards. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/22/19 1:02 PM, Juan Erbes wrote:
El jue., 21 feb. 2019 a las 17:07, stakanov (<stakanov@eclipso.eu>) escribió:
Larry Thanks. For what it is good for: the installation is for testing purposes and to see if migrated my laptop and files will perform as desired. The question was more to understand if this is a bug to be reported or not. It seems it is not. Currently I am still trying to a) import an archive of kmail into the new account with postgres10. If I succeed I will try to upgrade another similar account from 9.6 to 10. All for learning purposes, so you see, I have a lot of
[...]>> things to do. Thank you for the heads up. Regards.
Have you ensured that the partitioner does not partition and format the existing /home partition? It has happened to me with a previous version of 15.1 alpha, in the PC of a friend, who later wanted to kill me for the loss of all the information
Well, we (the YaST team) are still waiting for a bug report about that containing the logs of that installation. Because, as I originally pointed in the original thread, the situation is quite unlikely to have happened in the exact way you described it. See https://lists.opensuse.org/opensuse-factory/2018-11/msg00303.html Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Ancor Gonzalez Sosa -
Carlos E. R. -
Juan Erbes -
Larry Finger -
stakanov