Any movement?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Title:
beegfs-meta lockup with glibc 2.27 on bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
This bug is affecting our systems as well.
I just wanted to note that the torel's workaround of disabling updatedb
indexing of beegfs metadata may work for specific uses of beegfs, but
it would not fix the problem for us. Our users regularly generate large
number of files in cluster jobs, causing
WorkARound is adding beegfs to PRUNEFS and mountpoint to PRUNEPATHS in
/etc/updatedb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Title:
beegfs-meta lockup with glibc 2.27 on bionic
T
Debug of this mornings lockup.
** Attachment added: "beegfs-meta-gdb.log"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1844195/+attachment/5393597/+files/beegfs-meta-gdb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "beegfs-meta-gdb2.log"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1844195/+attachment/5393090/+files/beegfs-meta-gdb2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
gdb of locked beegfs-meta. Will have to redo. Forgot stdout.
** Attachment added: "beegfs-meta-gdb.log"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1844195/+attachment/5393089/+files/beegfs-meta-gdb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Sounds like something possibly was checked into glibc (libc6 on ubuntu)
between
libc6:amd64 2.27-3ubuntu1 amd64 GNU C Library:
Shared libraries
and
libc6:amd64 2.27-3ubuntu1.2 amd64
Which check-in is the culprit in
https://launchpad.net/ubuntu/+source/glibc/2.27-
Been seeing the same, but it has escalated to the point that it occurs
every morning at 6:30-6:40am.
root@srl-mds1:~# uname -ar
Linux srl-mds1 4.15.0-109-generic #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
root@srl-mds1:~# dpkg -l libc6
Desired=Unknown/Install/R
Just a followup as this issue was reported about a month ago, I wonder
if there is anyone from the GLIBC team who could have a look at this
code?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Really curious if this turns out to be a glibc problem or a beegfs-meta
problem, but we were able to hack together something that circumvents
this problem by forcing beegfs-meta to use an older glibc6 (from
xenial). beegfs-meta is now stable and performing much better!
There's probably a simpler
I also experience the issue but not at specific times but on medium/high
load situations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Title:
beegfs-meta lockup with glibc 2.27 on bionic
T
beegfs-meta went into high CPU lock-up again today, at 6:27:07 am, even
with daily updates disabled. So apt-daily-upgrade is not directly
related to the hangs.
It turns out though that there is other stuff scheduled around that time
by daily cron:
25 6* * * roottest -x /usr/sbin/anacron
Seeing the same issue on the same configuration, but occurs every 24h,
to within a few minutes or seconds after the following systemd timer
goes off.
Sat 2019-10-05 06:41:41 EDT 21h leftFri 2019-10-04 06:33:12 EDT 2h
59min ago apt-daily-upgrade.timer apt-daily-upgrade.service
The updat
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Title:
beeg
Hi, we also have the same issue.
Release: Ubuntu 18.04.3 bionic
Kernel: 4.15.0-62-generic
libc6: 2.27-3ubuntu1
beegfs: 7.1.3
Not ideal, of course, but going to try and run beegfs-meta in a chrooted
xenial (using the xenial glibc version).
--
You received this bug notification because you are a
Hi, we have the same issue. I can confirm that after attaching gdb to
the beegfs-meta process, it resumes normal operation.
On our system it seems the issue is recuring more or less around 24h.
Release: Ubuntu 18.04.1 bionic
Kernel: 4.15.0-39-generic
libc6: 2.27-3ubuntu1
beegfs: 7.1.1
--
You re
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844195
Title:
beegfs-meta lockup with glibc 2.27 on bionic
To manage notification
18 matches
Mail list logo
