Bug 763324 (GLUSTER-1592) - Core dump in 3.0.5 while creating huge number of files
Summary: Core dump in 3.0.5 while creating huge number of files
Keywords:
Status: CLOSED DUPLICATE of bug 763719
Alias: GLUSTER-1592
Product: GlusterFS
Classification: Community
Component: quota
Version: 3.0.5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-13 11:26 UTC by Sachidananda Urs
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Information to core (224.00 KB, application/x-gzip)
2010-09-13 08:27 UTC, Sachidananda Urs
no flags Details

Description Sachidananda Urs 2010-09-13 08:27:22 UTC
Created attachment 308

Comment 1 Sachidananda Urs 2010-09-13 11:26:29 UTC
Attached are the volume files, logs, and core file.

Comment 2 Amar Tumballi 2010-09-14 13:45:22 UTC
tried with removing following lines in pump.c, things worked fine..


diff --git a/xlators/cluster/afr/src/pump.c b/xlators/cluster/afr/src/pump.c
index 977de07..bdce874 100644
--- a/xlators/cluster/afr/src/pump.c
+++ b/xlators/cluster/afr/src/pump.c
@@ -1807,34 +1807,21 @@ fini (xlator_t *this)
 struct xlator_fops fops = {
        .lookup      = afr_lookup,
        .open        = afr_open,
-       .lk          = afr_lk,
        .flush       = afr_flush,
-       .statfs      = afr_statfs,
        .fsync       = afr_fsync,
-       .fsyncdir    = afr_fsyncdir,
        .xattrop     = afr_xattrop,
        .fxattrop    = afr_fxattrop,
-       .inodelk     = afr_inodelk,
-       .finodelk    = afr_finodelk,
-       .entrylk     = afr_entrylk,
-       .fentrylk    = afr_fentrylk,
 
        /* inode read */
-       .access      = afr_access,
-       .stat        = afr_stat,
-       .fstat       = afr_fstat,
-       .readlink    = afr_readlink,
        .getxattr    = pump_getxattr,
-       .readv       = afr_readv,
 
        /* inode write */
        .writev      = afr_writev,
        .truncate    = afr_truncate,
        .ftruncate   = afr_ftruncate,
        .setxattr    = pump_setxattr,
-        .setattr     = afr_setattr,
-       .fsetattr    = afr_fsetattr,
-       .removexattr = afr_removexattr,
+//        .setattr     = afr_setattr,
+//        .fsetattr    = afr_fsetattr,
 
        /* dir read */
        .opendir     = afr_opendir,

Comment 3 Amar Tumballi 2010-09-14 13:46:01 UTC
oops, should have been update for bug 763317.. sorry for confution

Comment 4 Amar Tumballi 2010-09-18 03:59:07 UTC
crash backtrace:

patchset: v3.0.2-41-g029062c
signal received: 11
time of crash: 2010-08-20 10:17:08
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.0.3
/lib64/libc.so.6[0x3f06a302d0]
/lib64/libc.so.6(strlen+0x30)[0x3f06a796f0]
/usr/local/glusterfs/3.0.3/lib/glusterfs/3.0.3/xlator/storage/posix.so(posix_setxattr+0x4f)[0x2b3e4922209f]
/usr/local/glusterfs/3.0.3/lib/glusterfs/3.0.3/xlator/features/quota.so(gf_quota_cache_sync+0x13d)[0x2b3e4943688d]
/usr/local/glusterfs/3.0.3/lib/glusterfs/3.0.3/xlator/features/quota.so(fini+0x13)[0x2b3e49436953]
/usr/local/glusterfs/3.0.3/sbin/glusterfsd(cleanup_and_exit+0x11b)[0x402ccb]
/lib64/libc.so.6[0x3f06a302d0]
/lib64/libc.so.6(epoll_wait+0x58)[0x3f06ad4018]
/usr/local/glusterfs/3.0.3/lib/libglusterfs.so.0[0x2b3e4877b9d2]
/usr/local/glusterfs/3.0.3/sbin/glusterfsd(main+0x9d8)[0x404118]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3f06a1d994]
/usr/local/glusterfs/3.0.3/sbin/glusterfsd[0x4026c9]


Notice that they are using quota translator, which is not well tested.. we will be addressing this soon.. hopefully we can address these things in 3.1.1+ releases.

Comment 5 Amar Tumballi 2010-09-18 04:00:46 UTC
OOps... this is happening because of 'fini()' called in some weird order.. Just need to handle fini() cases properly..

Also, note that the crash is happening after they are killing the process.. hence its very low priority.

Comment 6 Pranith Kumar K 2011-01-21 05:36:43 UTC

*** This bug has been marked as a duplicate of bug 1987 ***


Note You need to log in before you can comment on or make changes to this bug.