Hm, it's been a while...
I think back then I made some btrfs developers aware of it on IRC, but never
got around to sending it to the mailing list.
I'm running my own kernel builds for now (I had to do that to fix some other
issues anyway) with the patch from comment #4 applied, which seems to re
So far I have not been able to reproduce it on the mainline kernel linked above.
However, given the intermittent nature of the problem, I'm not convinced that
this was actually fixed.
The source code related to the underlying root cause looks unchanged, and the
symptoms may well be hidden away fo
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1765998
Title:
FS ac
I can confirm that the issue still exists in the mainline kernel build
linked above.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1765998
Title:
FS access deadlock with btrfs quotas en
This patch seems to fix it for me (running that for several days now).
** Patch added: "0002-qgroup_accounting_fix.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765998/+attachment/5126022/+files/0002-qgroup_accounting_fix.patch
--
You received this bug notification because you
I cannot run the affected (production) system using a broken kernel, and it
will lockup after boot within seconds.
If necessary, I can provide additional information or testing upon request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificati
** Description changed:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container s
The cause of the issue is already understood, and the machine currently isn't
running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this b
Public bug reported:
I'm running into an issue on Ubuntu Bionic (but not Xenial) where
shortly after boot, under heavy load from many LXD containers starting
at once, access to the btrfs filesystem that the containers are on
deadlocks.
The issue is quite hard to reproduce on other systems, quite
Public bug reported:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container start/stop
o
10 matches
Mail list logo
