[Bug 249380] New: bad suggestion to format /home, inconsistent default (still reiser)
https://bugzilla.novell.com/show_bug.cgi?id=249380 Summary: bad suggestion to format /home, inconsistent default (still reiser) Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: fehr@novell.com ReportedBy: sbrabec@novell.com QAContact: jsrain@novell.com Trying to install openSUSE 10.2 on my home machine, it offered to create and format /home partition, which was already ext3 formatted. This suggestion is invalid on almost 100% of cases - most people with separate /home want to save its contents after installation. During manual repartitioning, it still offers reiserfs as default, if I click to "Format". I guess it should be ext3. Logs placed to: ~sbrabec/var_log_YaST2_utx Suggestions to improvement: If /home partition already caries linux-friendly filesystem (ext*, xfs, reiser*), never offer formatting. While formatting partitions to file system, which supports it, use "Last mounted on" entry to properly identify disc structure on next installation. If more version of SuSE Linux is found in several partitions, the oldest one should be scheduled to be overwritten. When suggesting to format, don't inherit label from previous partition contents. Especially for / it causes nonsenses (e. g. openSUSE 10.1 with label "Gentoo Linux"). When switching to format, ext2 should be default, not reiserfs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from fehr@novell.com 2007-02-27 09:42 MST ------- Proposal could of course be rewritten according to your suggestions but this is certainly something to be decided by project management since it would mean throwing away current posprosal code and writing new one that can fulfil your requests. - currently nothing about content of partitions is known besides fs type Of could we could mount every block device and analyze content but I an already getting complains about slow startup times now. Mounting dozens of potentially incosistent filesystems will certainly not make startup faster - "last mounted on" is not available for reiserfs (no idea about xfs) Some remarks on things I can change easily: - When switching to "format" the currently detected fs is default. Which is IMHO ok, but you are right that the default should be ext3 if no previous fs was detectd. Will fix that. - Resetting the label when formatting is suggested by proposal code makes sense. Will fix that also. Generally resetting the label when formatting is IMHO not desirable if someone gives label names like "root", "home", "swap" he would probably be pissed if these are destroyed whenever he formats a filesystem. You other request would mean fundamental changes and I would only change these if dist team backs up your suggestions and of course is willing to live with the considerably increased startup time in some cases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |sbrabec@novell.com ------- Comment #2 from fehr@novell.com 2007-02-27 10:20 MST ------- I just tried to find a case where the partition create/edit dialog does default to reiserfs and was unsuccessful. It should only default to reiserfs if reiserfs is the detected filesystem on a partition (which is ok since of there is a fs detected this should be the default also when format is set to true). Please apply the following patch to /usr/share/YaST2/include/partitioning/custom_part_dialogs.ycp, it activates some more debug output of default fs selection. BTW: Lagrange:~ > ls -l ~sbrabec/var_log_YaST2_utx/ ls: /suse/sbrabec/var_log_YaST2_utx/YaST2: Permission denied -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 ------- Comment #3 from fehr@novell.com 2007-02-27 10:20 MST ------- Created an attachment (id=121353) --> (https://bugzilla.novell.com/attachment.cgi?id=121353&action=view) activate more debug output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sbrabec@novell.com | ------- Comment #4 from sbrabec@novell.com 2007-02-27 11:04 MST ------- To comment #2: This is my case. I expected ext3 as unconditional default in the expert partitioner, too. Previous system was SuSE Linux 10.0 on reiserfs, which was scheduled to be overwritten. Now I expected ext3 as default for /. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #5 from fehr@novell.com 2007-02-28 02:54 MST ------- ext3 is only default for three cases: - when a partition is formatted in a proposal - when a new partition/LV/MD is created - when a partition/LV/MD is edited and no filesystem is detected. Since there are valid reasons to deviate from the default filesystem I do not consider it useful to always change the filesystem to ext3 whenever the user activates format. It worked this way since yast2 partitioner exists and so far nobody complained. Meanwhile I changed proposal code to automatically remove labels. Your other suggestions would mean fundmental changes to current proposal functionality and I will only implement such things if dist team approves it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | Summary|bad suggestion to format |bad suggestion to format /home |/home, inconsistent default | |(still reiser) | ------- Comment #6 from sbrabec@novell.com 2007-02-28 03:23 MST ------- It was only one part of the bug. Remaining issues: Trying to install openSUSE 10.2 on my home machine, it offered to format /home partition, which was already ext3 formatted. This suggestion is invalid on almost 100% of cases - most people with separate /home want to save its contents after installation. Logs placed to: ~sbrabec/var_log_YaST2_utx Proposals to improve: If /home (and maybe some others) partitions already caries linux-friendly filesystem (ext*, xfs, reiser*), never offer formatting. While formatting partitions to file system, which supports it, fill "Last mounted on" entry to properly identify disc structure on next installation. If more version of SuSE Linux is found in several partitions, the oldest one should be scheduled to be overwritten. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Comment #7 from fehr@novell.com 2007-02-28 03:51 MST ------- The bug was resolved as WONTFIX. Reasons were explianed in my comments. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380 jonharson@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.jaeger@rub.de ------- Comment #8 from jonharson@gmail.com 2007-05-23 14:58 MST ------- *** Bug 277582 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=249380#c9
Matej Horvath
https://bugzilla.novell.com/show_bug.cgi?id=249380#c10
--- Comment #10 from Hubert Figuiere
https://bugzilla.novell.com/show_bug.cgi?id=249380#c11
--- Comment #11 from Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380#c12
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=249380#c13
Larry Ewing
https://bugzilla.novell.com/show_bug.cgi?id=249380#c14
--- Comment #14 from Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380#c15
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380
Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380#c16
Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380#c17
--- Comment #17 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=249380#c18
--- Comment #18 from Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380#c19
--- Comment #19 from Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380#c20
--- Comment #20 from Richard Creighton
Since 10.3 development is over now, I will implement code in STABLE (while will become next openSuSE/SLES release) that look at the fs intended to be used for /home and suppresses formatting if heuristics indicate it is a valid /home filesystem.
I still consider this a bogus feature since it involves mounting a potetially large filesystem with unknown content and state. If the filesystem happens to be dirty, the log replay alone may take minutes and there is no save way to prevent these minutes to be wasted, but in the end it is probably less time consuming to implement that stuff than to discuss this forever.
I suggest then making a pop-up dialog when this occurs and let the operator make the decision. There are already many delays in the installation but one the operator is willing to make is one that saves time in the long run and reconstruction of data structures inadvertently erased or formatted takes longer than remounting a dirty partition and by asking you have alerted the operator and if there is a delay, he also now knows the reason. If they don't want to save the existing data/structure, proceed as you currently propose to do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=249380#c21
--- Comment #21 from Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380#c22
--- Comment #22 from Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380#c23
--- Comment #23 from Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380#c24
--- Comment #24 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=249380#c25
--- Comment #25 from Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380#c26
--- Comment #26 from Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380#c27
--- Comment #27 from Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380#c28
--- Comment #28 from Christian Jäger
https://bugzilla.novell.com/show_bug.cgi?id=249380
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380#c29
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380
Federico Mena Quintero
https://bugzilla.novell.com/show_bug.cgi?id=249380
User fehr@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=249380#c30
Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=249380
User federico@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=249380#c31
--- Comment #31 from Federico Mena Quintero
participants (1)
-
bugzilla_noreply@novell.com