[Bugs] [Bug 1321554] New: assert failure happens when parallel rm -rf is issued on nfs mounts
bugzilla at redhat.com
bugzilla at redhat.com
Mon Mar 28 11:34:21 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1321554
Bug ID: 1321554
Summary: assert failure happens when parallel rm -rf is issued
on nfs mounts
Product: GlusterFS
Version: mainline
Component: replicate
Assignee: bugs at gluster.org
Reporter: pkarampu at redhat.com
CC: bugs at gluster.org
Description of problem:
(gdb) bt
#0 0x00007f652b091a98 in __GI_raise (sig=sig at entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x00007f652b09369a in __GI_abort () at abort.c:89
#2 0x00007f652b08a227 in __assert_fail_base (fmt=<optimized out>,
assertion=assertion at entry=0x7f652c5a529c "inode->nlookup >=
nlookup", file=file at entry=0x7f652c5a512a "inode.c", line=line at entry=711,
function=function at entry=0x7f652c5a5848 <__PRETTY_FUNCTION__.10534>
"__inode_forget") at assert.c:92
#3 0x00007f652b08a2d2 in __GI___assert_fail (
assertion=0x7f652c5a529c "inode->nlookup >= nlookup",
file=0x7f652c5a512a "inode.c", line=711,
function=0x7f652c5a5848 <__PRETTY_FUNCTION__.10534>
"__inode_forget") at assert.c:101
#4 0x00007f652c5203e8 in __inode_forget (inode=0x7f6504038aec,
---Type <return> to continue, or q <return> to quit---
nlookup=1) at inode.c:711
#5 0x00007f652c5210f8 in inode_forget (inode=0x7f6504038aec,
nlookup=1) at inode.c:1123
#6 0x00007f651f75258c in afr_lookup_sh_metadata_wrap (
opaque=0x7f65180a9b3c) at afr-common.c:1928
#7 0x00007f652c54d925 in synctask_wrap (old_task=0x7f65040467b0)
at syncop.c:375
#8 0x00007f652b0a5f10 in ?? () from /lib64/libc.so.6
#9 0x0000000000000000 in ?? ()
(gdb) f 4
#4 0x00007f652c5203e8 in __inode_forget (inode=0x7f6504038aec,
nlookup=1) at inode.c:711
711 GF_ASSERT (inode->nlookup >= nlookup);
(gdb) p inode->nlookup
$1 = 0
(gdb) p nlookup
$2 = 1
(gdb)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list