From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 107301] New: system hang during ext4 xattr operation
Date: Thu, 05 Nov 2015 13:54:24 +0000 [thread overview]
Message-ID: <bug-107301-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=107301
Bug ID: 107301
Summary: system hang during ext4 xattr operation
Product: File System
Version: 2.5
Kernel Version: 4.2.3 3.19 3.16
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: sileht@sileht.net
Regression: No
Created attachment 192191
--> https://bugzilla.kernel.org/attachment.cgi?id=192191&action=edit
dmesg received via netconsole before the system hang
Hi,
We are running a ceph cluster on ext4 filesystem, we recently got a hardware
failure, the ceph recovery process provokes a huge amount of data write on all
our ext4 filesystems (~40 disks).
Now, we are experienced random nodes hang, we catch some partial backtrace
(that can be found on the ceph bug tracker). And recently we got the full dmesg
log via netconsole (attached to this BZ).
When the freeze occurs, it seems ceph processes lockup all the CPUs, each CPUs
backtrace is related to a xattr operation.
bug report on ceph side: http://tracker.ceph.com/issues/13662
We have some nodes on debian and some other on ubuntu, we tried kernels 3.16,
3.19, 4.2.3. The issue occurs with all of them.
Cheers,
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-11-05 13:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 13:54 bugzilla-daemon [this message]
2015-11-05 15:45 ` [Bug 107301] system hang during ext4 xattr operation bugzilla-daemon
2015-11-05 17:02 ` bugzilla-daemon
2015-11-05 17:41 ` bugzilla-daemon
2015-11-06 2:43 ` bugzilla-daemon
2015-11-06 20:29 ` bugzilla-daemon
2015-11-07 15:24 ` bugzilla-daemon
2015-11-07 17:58 ` bugzilla-daemon
2015-11-09 8:50 ` bugzilla-daemon
2015-11-09 9:24 ` bugzilla-daemon
2015-11-09 10:11 ` bugzilla-daemon
2015-11-09 14:31 ` bugzilla-daemon
2015-11-09 15:22 ` bugzilla-daemon
2015-11-09 18:13 ` bugzilla-daemon
2015-11-10 11:16 ` bugzilla-daemon
2015-11-11 2:37 ` bugzilla-daemon
2015-11-11 10:28 ` bugzilla-daemon
2015-11-11 11:37 ` bugzilla-daemon
2015-11-11 14:53 ` bugzilla-daemon
2015-11-18 20:48 ` bugzilla-daemon
2015-11-19 0:49 ` bugzilla-daemon
2015-11-19 15:11 ` bugzilla-daemon
2015-12-10 2:51 ` bugzilla-daemon
2015-12-10 16:51 ` bugzilla-daemon
2016-03-31 13:53 ` bugzilla-daemon
2016-04-08 10:09 ` bugzilla-daemon
2016-04-08 20:46 ` bugzilla-daemon
2016-04-12 12:52 ` bugzilla-daemon
2016-04-13 9:07 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107301-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.