Bug 1043373 - brick server kernel panic on ext4
Summary: brick server kernel panic on ext4
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: posix
Version: 3.3.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Niels de Vos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 06:40 UTC by ihavenoemail
Modified: 2014-08-12 15:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-12 15:29:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
screen shot when kenal panic (924.74 KB, image/jpeg)
2013-12-16 06:40 UTC, ihavenoemail 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description ihavenoemail 2013-12-16 06:40:21 UTC 
Created attachment 837120 [details]
screen shot when kenal panic

Description of problem:
We are running gluster on Centos 6.2,ex4 brick.
sometimes we ran into kenal panic on brick servers,we have to reboot brick server.

Version-Release number of selected component (if applicable):


How reproducible:
very hard

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Niels de Vos 2014-08-12 15:29:59 UTC 
Partial call trace from the screenshot:

...
ext4_xattr_trusted_set
generic_setxattr
__vfs_setxattr_noperm
vfs_setxattr
setxattr
...

RIP at ext4_mb_free_blocks


This definitely is a kernel bug, not a GlusterFS one. Please file a bug at the CentOS Bug Tracker (http://bugs.centos.org). Mention the version of the kernel that you are using, and if possible capture a full stacktrace (use netconsole, a serial console or setup kdump).

Closing this now, we cant fix this in GlusterFS.
Note You need to log in before you can comment on or make changes to this bug.