Bug 764584 (GLUSTER-2852)
| Summary: | Glusterfsd crashes on AMI | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Saurabh <saurabh> |
| Component: | core | Assignee: | Raghavendra G <raghavendra> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | christopher.anderlik, gluster-bugs, jacob, vijay |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Saurabh
2011-04-27 09:54:06 UTC
*** Bug 2853 has been marked as a duplicate of this bug. *** PATCH: http://patches.gluster.com/patch/7064 in master (marker: fix NULL deref in logging) it happened again on tokyo region, [2011-05-03 11:02:48.686121] E [access-control.c:1842:ac_setattr_stat_cbk] 0-dist-rep-access-control: setattr failed with error: Operation not permitted pending frames: patchset: v3.2.0 signal received: 11 time of crash: 2011-05-03 11:02:48 configuration details: argp 1 backtrace 1 dlfcn 1 fdatasync 1 libpthread 1 llistxattr 1 setfsid 1 spinlock 1 epoll.h 1 xattr.h 1 st_atim.tv_nsec 1 package-string: glusterfs 3.2.0 /lib64/libc.so.6[0x2aaaab9b62d0] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/marker.so(marker_setattr_cbk+0x139)[0x2aaaad983e79] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_setattr_cbk+0x88)[0x2aaaad773718] /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(default_setattr_cbk+0x88)[0x2aaaaaef1f28] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/access-control.so(ac_setattr_stat_cbk+0x137)[0x2aaaad354ec7] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/storage/posix.so(posix_stat+0x14d)[0x2aaaad13cbfd] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/access-control.so(ac_setattr+0x14c)[0x2aaaad350a7c] /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(default_setattr+0xe9)[0x2aaaaaeeb659] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_setattr_wrapper+0xe9)[0x2aaaad776749] /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(call_resume+0xd81)[0x2aaaaaefc191] /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_worker+0x119)[0x2aaaad77a229] /lib64/libpthread.so.0[0x2aaaab770617] /lib64/libc.so.6(clone+0x6d)[0x2aaaaba59c2d] --------- [root@ip-10-150-138-205 ~]# hostname -f ip-10-150-138-205.ap-northeast-1.compute.internal [root@ip-10-150-138-205 ~]# Saurabh, are you using a release which contained the fix (http://patches.gluster.com/patch/7064)? Seems the version you are using does not contain the fix. regards, (In reply to comment #4) > it happened again on tokyo region, > > > [2011-05-03 11:02:48.686121] E [access-control.c:1842:ac_setattr_stat_cbk] > 0-dist-rep-access-control: setattr failed with error: Operation not permitted > pending frames: > > patchset: v3.2.0 > signal received: 11 > time of crash: 2011-05-03 11:02:48 > configuration details: > argp 1 > backtrace 1 > dlfcn 1 > fdatasync 1 > libpthread 1 > llistxattr 1 > setfsid 1 > spinlock 1 > epoll.h 1 > xattr.h 1 > st_atim.tv_nsec 1 > package-string: glusterfs 3.2.0 > /lib64/libc.so.6[0x2aaaab9b62d0] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/marker.so(marker_setattr_cbk+0x139)[0x2aaaad983e79] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_setattr_cbk+0x88)[0x2aaaad773718] > /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(default_setattr_cbk+0x88)[0x2aaaaaef1f28] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/access-control.so(ac_setattr_stat_cbk+0x137)[0x2aaaad354ec7] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/storage/posix.so(posix_stat+0x14d)[0x2aaaad13cbfd] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/features/access-control.so(ac_setattr+0x14c)[0x2aaaad350a7c] > /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(default_setattr+0xe9)[0x2aaaaaeeb659] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_setattr_wrapper+0xe9)[0x2aaaad776749] > /opt/glusterfs/3.2.0/lib64/libglusterfs.so.0(call_resume+0xd81)[0x2aaaaaefc191] > /opt/glusterfs/3.2.0/lib64/glusterfs/3.2.0/xlator/performance/io-threads.so(iot_worker+0x119)[0x2aaaad77a229] > /lib64/libpthread.so.0[0x2aaaab770617] > /lib64/libc.so.6(clone+0x6d)[0x2aaaaba59c2d] > --------- > > > > [root@ip-10-150-138-205 ~]# hostname -f > ip-10-150-138-205.ap-northeast-1.compute.internal > [root@ip-10-150-138-205 ~]# Hello Raghavendra, I was given the new AMI after the patch was fixed, so by default I thought that the patch is propagated to the new AMI's also. Hence, I re-opened the bug, whereas after discussion with Avati came to know that he is going to make knew AMIs having the patch included. Requesting you to keep it open till the AMI's are tested, if this issue is not found again I will move it back to Resolved/Verified state. Thanks Saurabh Executed the posix compliance test over nfs/fuse mounts on the filesystem for 3.2.1qa2, and didn't find this issue happening. *** Bug 3014 has been marked as a duplicate of this bug. *** *** Bug 3027 has been marked as a duplicate of this bug. *** I can confirm that the problem is solved in 3.2.1 thank you guys! |