[Bug 1099769] New: btrfs balance generates 100% CPU usage for long periods (15min's +)
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769 Bug ID: 1099769 Summary: btrfs balance generates 100% CPU usage for long periods (15min's +) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: chris@kuta.bid QA Contact: qa-bugs@suse.de Found By: Community User Blocker: --- System becomes unresponsive for long periods (15 minutes or more). 'top' command indicates btrfs process using 100% CPU. Previously reported bug is still not fixed IMHO. * Please advise which logs would be helpful & how to generate on OpenSUSE Tumbleweed. Recently installed & updated OpenSUSE Tumbleweed. KDE desktop. Kernel 4.17.2-1-default. Regards -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769
Chris .
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769#c1
--- Comment #1 from Chris .
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769#c2
Adam Szyszko
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769#c5
Bruno Friedmann
From memory as it is not possible to mount or grab information from the defect volume.
BTW ; What's written in the wiki https://en.opensuse.org/SDB:BTRFS btrfs scrub start /dev/mapper/cr_nvme0n1p2 doesn't work it state error not mounted filesystem ? What's the problem as it should normally possible to use a device (here the cryptsetup luksOpen /dev/nvmen0p2 cr_nvme0n1p2 unlocked device) It's the first time since one year the system is installed, that this happen. The only things that have changed, is a lot of newer data in (up to 85% used) and numerous file and directories cleanup yesterday afternoon. What is the best possible recovery scenario ? and the best forensic approach to debug this nasty behaviour. any tricks is welcomed. In the meantime I will at least retry to mount it ro and use a btrfs dump. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1099769
Alan Prescott
participants (1)
-
bugzilla_noreply@novell.com