today's kernel update seems to have fixed it, as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890951
Title:
btrfs not writable when mounted without "skip_balance"
To manage
Also see:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890951
Title:
btrfs not writable when mounted without "skip_balance"
To manage
** No longer affects: linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890951
Title:
btrfs not writable when mounted without "skip_balance"
To manage notifications about this bug go to:
apparently fixed in kernel 5.4.56
https://lore.kernel.org/linux-btrfs/8a3370fd-7cda-78d2-b036-8350c5a3e...@gmx.com/T/#r52f03985dd7982c8f92c8a65089583f01c62020b
Will it become available for Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Apparently this is (probably) fixed in kernels from 5.4.54
https://lore.kernel.org/linux-btrfs/8a3370fd-7cda-
78d2-b036-8350c5a3e...@gmx.com/T/#r52f03985dd7982c8f92c8a65089583f01c62020b
so I hope it becomes available in Ubuntu soon.
--
You received this bug notification because you are a member
Launchpad has imported 10 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=203405.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: Linux Kernel Bug Tracker #203405
https://bugzilla.kernel.org/show_bug.cgi?id=203405
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=203405
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
apport information
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected focal
** Description changed:
Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem
with the btrfs volume it is installed on. The system hung when launching
a
Unfortunately, producing the logs apart from the backtrace above isn't
really possible. As soon as I reproduce the bug, the FS becomes
unwritable, so that no logs can be obtained. That's a catch22
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug
