[opensuse-factory] btrfs woes
Hi list, my laptop just died away while running. First thought it was an application error (kstars/EKOS), as that one stoped updating, while e.g. my emacs still worked. But after some 10 more seconds everything stoped responding, and I finally had to press the power button. After that, the system boot would hang reproducably telling me it's waiting for ridiculous stuff like saving the kill switch state, flushing the journal to persistent storage and some 2 others I couldn't remember. After three unsuccessful trials, I booted from a rescue disk. Expecting bad things, I tried mounting my root partition - but it did so without complaints. To be sure, I ran an 'btrfs scrub start /mnt' that finished after some 1-2 minutes. Not really having more ideas I rebooted, and now the system came up fine. Looking at the last logfile entries I see it was running btrfsmainainance, doing trim and balance. URL: http://paste.opensuse.org/24906643 Interesting cutouts are May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: /dev/sda2 73G 67G 5.6G 93% / .... May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=1 -susage=1 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags metadata May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): found 2 extents May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): 1 enospc errors during balance May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: ended with status: -28 May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: ERROR: error during balancing '/': No space left on device ..... May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate 1 out of 84 chunks May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=10 -susage=10 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags system May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398815395840 flags metadata May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file: fs/btrfs/relocation.c, line: 804 May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------ May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518! That's where the log ends. Not sure what to do with this. Why is it running out of space with 5.6G left? what are those two last messages? Should this go to bugzilla? Even without proper/complete error messages? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 27 May 2019 02.12.51 CEST Peter Suetterlin wrote:
Hi list,
my laptop just died away while running. First thought it was an application error (kstars/EKOS), as that one stoped updating, while e.g. my emacs still worked. But after some 10 more seconds everything stoped responding, and I finally had to press the power button.
After that, the system boot would hang reproducably telling me it's waiting for ridiculous stuff like saving the kill switch state, flushing the journal to persistent storage and some 2 others I couldn't remember.
After three unsuccessful trials, I booted from a rescue disk. Expecting bad things, I tried mounting my root partition - but it did so without complaints.
To be sure, I ran an 'btrfs scrub start /mnt' that finished after some 1-2 minutes. Not really having more ideas I rebooted, and now the system came up fine.
Looking at the last logfile entries I see it was running btrfsmainainance, doing trim and balance. URL: http://paste.opensuse.org/24906643
Interesting cutouts are May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: /dev/sda2 73G 67G 5.6G 93% / .... May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=1 -susage=1 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags metadata May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): found 2 extents May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): 1 enospc errors during balance May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: ended with status: -28 May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: ERROR: error during balancing '/': No space left on device ..... May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate 1 out of 84 chunks May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=10 -susage=10 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags system May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398815395840 flags metadata May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file: fs/btrfs/relocation.c, line: 804 May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------ May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518!
That's where the log ends. Not sure what to do with this. Why is it running out of space with 5.6G left? what are those two last messages?
I can not really answer both those questions however running into "out of space" myself even though there should be enough free space (and metadata space) I deleted more data until all subsequent balance runs with the increasing "-musage" and "-susage" numbers successfully finished.
Should this go to bugzilla? Even without proper/complete error messages?
I looked on bugzilla and did not find a report with the specific line "kernel BUG at fs/btrfs/ctree.h:3518!" so I recommend to report a bug. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 27 May 2019 02.12.51 CEST Peter Suetterlin wrote:
Hi list,
my laptop just died away while running. First thought it was an application error (kstars/EKOS), as that one stoped updating, while e.g. my emacs still worked. But after some 10 more seconds everything stoped responding, and I finally had to press the power button.
After that, the system boot would hang reproducably telling me it's waiting for ridiculous stuff like saving the kill switch state, flushing the journal to persistent storage and some 2 others I couldn't remember.
After three unsuccessful trials, I booted from a rescue disk. Expecting bad things, I tried mounting my root partition - but it did so without complaints.
To be sure, I ran an 'btrfs scrub start /mnt' that finished after some 1-2 minutes. Not really having more ideas I rebooted, and now the system came up fine.
Looking at the last logfile entries I see it was running btrfsmainainance, doing trim and balance. URL: http://paste.opensuse.org/24906643
Interesting cutouts are May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: /dev/sda2 73G 67G 5.6G 93% / .... May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=1 -susage=1 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags metadata May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): found 2 extents May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): 1 enospc errors during balance May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: ended with status: -28 May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: ERROR: error during balancing '/': No space left on device ..... May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate 1 out of 84 chunks May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=10 -susage=10 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags system May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398815395840 flags metadata May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file: fs/btrfs/relocation.c, line: 804 May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------ May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518!
That's where the log ends. Not sure what to do with this. Why is it running out of space with 5.6G left? what are those two last messages?
I can not really answer both those questions however running into "out of space" myself even though there should be enough free space (and metadata space) I deleted more data until all subsequent balance runs with the increasing "-musage" and "-susage" numbers successfully finished.
Should this go to bugzilla? Even without proper/complete error messages?
I looked on bugzilla and did not find a report with the specific line "kernel BUG at fs/btrfs/ctree.h:3518!" so I recommend to report a bug. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi all Just the regular reminder that this is the list for discussing development in openSUSE projects not peoples bug reports. If what you would like to discuss does not cover many packages and is nott about the bricking of most peoples Tumbleweed / Leap Beta, your likely posting in the wrong place. I'm not signaling out this post, its just an example when I got around to sending this. But the noise has been creeping up again, and I had complaints from oSC19 from several people who need to use this list to do there jobs that the noise is once again too high. Cheers Simon On 27/05/2019 09:42, Peter Suetterlin wrote:
Hi list,
my laptop just died away while running. First thought it was an application error (kstars/EKOS), as that one stoped updating, while e.g. my emacs still worked. But after some 10 more seconds everything stoped responding, and I finally had to press the power button.
After that, the system boot would hang reproducably telling me it's waiting for ridiculous stuff like saving the kill switch state, flushing the journal to persistent storage and some 2 others I couldn't remember.
After three unsuccessful trials, I booted from a rescue disk. Expecting bad things, I tried mounting my root partition - but it did so without complaints.
To be sure, I ran an 'btrfs scrub start /mnt' that finished after some 1-2 minutes. Not really having more ideas I rebooted, and now the system came up fine.
Looking at the last logfile entries I see it was running btrfsmainainance, doing trim and balance. URL: http://paste.opensuse.org/24906643
Interesting cutouts are May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: /dev/sda2 73G 67G 5.6G 93% / .... May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=1 -susage=1 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags metadata May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): found 2 extents May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): 1 enospc errors during balance May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: ended with status: -28 May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: ERROR: error during balancing '/': No space left on device ..... May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate 1 out of 84 chunks May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=10 -susage=10 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags system May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398815395840 flags metadata May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file: fs/btrfs/relocation.c, line: 804 May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------ May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518!
That's where the log ends. Not sure what to do with this. Why is it running out of space with 5.6G left? what are those two last messages? Should this go to bugzilla? Even without proper/complete error messages?
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 27/05/2019 19.30, Simon Lees wrote:
Hi all
Just the regular reminder that this is the list for discussing development in openSUSE projects not peoples bug reports.
If what you would like to discuss does not cover many packages and is nott about the bricking of most peoples Tumbleweed / Leap Beta, your likely posting in the wrong place.
I'm not signaling out this post, its just an example when I got around to sending this. But the noise has been creeping up again, and I had complaints from oSC19 from several people who need to use this list to do there jobs that the noise is once again too high.
May I suggest that people with knowledge in internals visit the opensuse-support@opensuse.org mail list periodically? When people do not get answers there, they turn to here. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 28/05/2019 03:30, Carlos E. R. wrote:
On 27/05/2019 19.30, Simon Lees wrote:
Hi all
Just the regular reminder that this is the list for discussing development in openSUSE projects not peoples bug reports.
If what you would like to discuss does not cover many packages and is nott about the bricking of most peoples Tumbleweed / Leap Beta, your likely posting in the wrong place.
I'm not signaling out this post, its just an example when I got around to sending this. But the noise has been creeping up again, and I had complaints from oSC19 from several people who need to use this list to do there jobs that the noise is once again too high.
May I suggest that people with knowledge in internals visit the opensuse-support@opensuse.org mail list periodically? When people do not get answers there, they turn to here.
There was no btrfs discussion in the last week or so on that mailing list. This is not a support mailing list or a bugtracker, people doing those things here will be told not to and to take it to one of the appropriate channels, if they do not listen it will be elevated to the board. Alongside the mailing list there are plenty of people willing to offer support on the forums, irc and discord. If something is broken we have a bugtracker so that you can notify the maintainer. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 27/05/2019 22.09, Simon Lees wrote:
On 28/05/2019 03:30, Carlos E. R. wrote:
On 27/05/2019 19.30, Simon Lees wrote:
Hi all
Just the regular reminder that this is the list for discussing development in openSUSE projects not peoples bug reports.
If what you would like to discuss does not cover many packages and is nott about the bricking of most peoples Tumbleweed / Leap Beta, your likely posting in the wrong place.
I'm not signaling out this post, its just an example when I got around to sending this. But the noise has been creeping up again, and I had complaints from oSC19 from several people who need to use this list to do there jobs that the noise is once again too high.
May I suggest that people with knowledge in internals visit the opensuse-support@opensuse.org mail list periodically? When people do not get answers there, they turn to here.
There was no btrfs discussion in the last week or so on that mailing list. This is not a support mailing list or a bugtracker, people doing those things here will be told not to and to take it to one of the appropriate channels, if they do not listen it will be elevated to the board.
I agree with that. Did not say anything to the contrary.
Alongside the mailing list there are plenty of people willing to offer support on the forums, irc and discord. If something is broken we have a bugtracker so that you can notify the maintainer.
Often questions on the specific support mail list go unanswered. I'm making the guess that then people resort to mail here. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 05/27/2019 04:34 PM, Carlos E. R. wrote:
I agree with that. Did not say anything to the contrary.
Alongside the mailing list there are plenty of people willing to offer support on the forums, irc and discord. If something is broken we have a bugtracker so that you can notify the maintainer. Often questions on the specific support mail list go unanswered. I'm making the guess that then people resort to mail here.
All a foreseeable consequence of fragmenting the mailing lists to the extent people really don't know where to post, and if they find the corner-case mailing list that fits, nobody responds. But at least the traffic on opensuse@opensuse.org had nearly dried up completely before 15.1 hit. -- David C. Rankin, J.D.,P.E.
Simon Lees wrote:
Hi all
Just the regular reminder that this is the list for discussing development in openSUSE projects not peoples bug reports.
Thanks. I'll be switching this list to RO mode. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Carlos E. R. -
David C. Rankin -
Oliver Kurz -
Peter Suetterlin -
Simon Lees