[Bug 1130702] New: Lockup during "zypper dup"
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 Bug ID: 1130702 Summary: Lockup during "zypper dup" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: nwr10cst-oslnx@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: I was updating to the latest build (Build438.2). After downloading the packages, the installation began. And it got to the point where I was seeing: ( 2/105) Installing: btrfsmaintenance-0.4.2-lp151.1.1.noarch ..<48%>========[-] It never budged beyond that 48%. I waited 10 minutes, with nothing happening. There was almost no cpu usage. Looking from another xterm, it appeared that the hangup was in: /usr/bin/systemctl try-restart btrfsmaintenance-refresh.service btrfsmaintenance-refresh.path btrfs-balance.service btrfs-balance.timer I terminated the "zypper" run with CTRL-C (twice). Restarting gave me an error about releasing a lock. So I rebooted (hoping to clear locks), and reran the "zypper" command. This time it completed successfully. But "btrfsmaintenance" was not listed as an installed package. For safety, I did a force reinstall of that package (using Yast, so it does not show up in my screenlog). As far as I can tell, all is now fine. But this should not have happened. I'm not sure where the blame lies. I will attach a couple of files with information. Reproducible: Didn't try -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 http://bugzilla.opensuse.org/show_bug.cgi?id=1130702#c1 --- Comment #1 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Created attachment 801361 --> http://bugzilla.opensuse.org/attachment.cgi?id=801361&action=edit screenlog (transcript of terminal session under "screen" running "zypper dup". I should have mentioned that I do not use "btrfs" on my system. The "screenlog.0" is just a transcript with "screen -L" of the session where I ran "zypper". Search for "btrfsmaint" to find the relevant lines. Repeat runs of "zypper dup" are in the same screenlog.0 file, including the repeat after a reboot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 http://bugzilla.opensuse.org/show_bug.cgi?id=1130702#c2 --- Comment #2 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Created attachment 801364 --> http://bugzilla.opensuse.org/attachment.cgi?id=801364&action=edit Output from "ps -ft pts/2" showing the zypper related commands This is from running "script" in a different terminal (xterm). I maximized that "xterm" so have as long lines as possible. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 http://bugzilla.opensuse.org/show_bug.cgi?id=1130702#c3 Jonathan Rivrain <jrivrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrivrain@suse.com Severity|Normal |Major --- Comment #3 from Jonathan Rivrain <jrivrain@suse.com> --- I had the same issue, while using btrfs. And this happened again with todays's zypper dup I hangs here: root 19347 0.0 0.0 59296 5780 pts/0 S+ 10:45 0:00 | | \_ /usr/bin/systemctl try-restart fstrim.service fstrim.timer Apr 01 09:29:11 linux-hh22 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Apr 01 10:45:28 linux-hh22 systemd[1]: fstrim.service: Main process exited, code=killed, status=15/TERM Apr 01 10:45:28 linux-hh22 systemd[1]: Stopped Discard unused blocks on filesystems from /etc/fstab. Apr 01 10:45:28 linux-hh22 systemd[1]: fstrim.service: Unit entered failed state. Apr 01 10:45:28 linux-hh22 systemd[1]: fstrim.service: Failed with result 'signal'. Apr 01 10:45:28 linux-hh22 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... The last time, I sorted it out by issuing the systemctl try-restart in another terminal, but this time it does not work. I have an un-ususal partition setup, my root being on two partitions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 http://bugzilla.opensuse.org/show_bug.cgi?id=1130702#c4 --- Comment #4 from Jonathan Rivrain <jrivrain@suse.com> --- Created attachment 801805 --> http://bugzilla.opensuse.org/attachment.cgi?id=801805&action=edit journalctl -u fstrim, btrfs fi show, ps faux, dmesg The command finally finished after 31 minutes, but last time (when upgrading btrfsmaintenance) it was not done after more than an hour. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1130702 http://bugzilla.opensuse.org/show_bug.cgi?id=1130702#c5 Neil Rickert <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- This appears to be a duplicate of bug 1110259 *** This bug has been marked as a duplicate of bug 1110259 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com