[Bug 946673] New: yast partitioner fails with gpt not using complete disk and broken backup table
http://bugzilla.suse.com/show_bug.cgi?id=946673 Bug ID: 946673 Summary: yast partitioner fails with gpt not using complete disk and broken backup table Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: aschnell@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- The YaST partitioner fails performing actions (e.g. create a partition) when the disk has a GPT not using the complete disk and the backup table is broken. The function Disk::enlargeGpt() is too simple for this scenario since the interactive parted first expects a "OK" and then a "Fix". Steps to reproduce: - truncate --size 1GiB image - parted -s image mklabel gpt - dd if=image of=/dev/sdb bs=1M count=1 - create partition on sdb in YaST -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Found By|--- |Development -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c1 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Lukas Ocilka <locilka@suse.com> --- Looks like a duplicate *** This bug has been marked as a duplicate of bug 946013 *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c2 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- --- Comment #2 from Arvin Schnell <aschnell@suse.com> --- No, it's not a duplicate. I found this one while working on bug #946013. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c3 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #3 from Lukas Ocilka <locilka@suse.com> --- I see. And is this openSUSE-only bug or is the same situation also in SLE 12 SP1? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c4 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aschnell@suse.com | |) | --- Comment #4 from Arvin Schnell <aschnell@suse.com> --- Should be the same situation in SLE 12 SP1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c5 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Assignee|yast2-maintainers@suse.de |jsrain@suse.com Flags| |needinfo?(jsrain@suse.com) --- Comment #5 from Lukas Ocilka <locilka@suse.com> --- Jiri, do you want to put this into the current or next sprint? RC1 is close. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |yast2-maintainers@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsrain@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Assignee|yast-internal@suse.de |aschnell@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c7 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |puzel@suse.com Flags| |needinfo?(puzel@suse.com) --- Comment #7 from Arvin Schnell <aschnell@suse.com> --- When parted detects that the GPT does not use the complete disk libstorage will fix it before the first partition change on the disk. Unfortunately parted can only fix the GPT in interactive mode and the class in libstorage to execute external commands cannot cope with interactive programs. As a simple workaround libstorage runs 'yes Fix | parted --pretend-input-tty ...'. This simple workaround fails when additionally the second table is broken. In that case parted needs input from the user twice, once "OK" to repair the second table and once "Fix" to make GPT cover the complete disk. So an improved workaround is to use 'echo -n "OK\\nFix" | parted --pretend-input-tty ...'. That all looks very fragile. Petr, would it be possible to add explicit commands to parted to repair and/or fix the GPT to avoid the interactive mode completely? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c9 --- Comment #9 from Arvin Schnell <aschnell@suse.com> --- Petr, please reply to comment #7. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c12 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(puzel@suse.com) --- Comment #12 from Arvin Schnell <aschnell@suse.com> --- Yes, for YaST that would be sufficient. I would recommend to fix the GPT only if it is written anyway. A pure print should not modify it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/kFGMe2 | |7S/1080-yast-partitioner-fa | |ils-with-gpt-not-using-comp | |lete-disk-and-broken-backup | |-table Assignee|aschnell@suse.com |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=946673 http://bugzilla.suse.com/show_bug.cgi?id=946673#c13 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #13 from Tomáš Chvátal <tchvatal@suse.com> --- This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com