GlusterFS FUSE Crashing with "Assertion failed: inode_lookup >= nlookup" #4074
Comments
mohit84
added a commit
to mohit84/glusterfs
that referenced
this issue
Sep 26, 2023
In ideal case the nlookup in kernel and fuse should be consistent but there is a case that fuse_direntplus_link would do nlookup++ and return fail due to that the counter is not consistent. To avoid a crash remove assertion and in case of value mismatch decrese the counter. > Fixes: gluster#4074 > Signed-off-by: ruanmeisi <ruan.meisi@zte.com.cn> > Reviwed on upstream link gluster#4081 > Cherry picked from commit a8486b9 Fixes: gluster#4074 Change-Id: Idd767cf1793dba6a4f6fd52f00dfb6810bbe4a8d Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Shwetha-Acharya
pushed a commit
that referenced
this issue
Oct 27, 2023
…4229) In ideal case the nlookup in kernel and fuse should be consistent but there is a case that fuse_direntplus_link would do nlookup++ and return fail due to that the counter is not consistent. To avoid a crash remove assertion and in case of value mismatch decrese the counter. > Fixes: #4074 > Signed-off-by: ruanmeisi <ruan.meisi@zte.com.cn> > Reviwed on upstream link #4081 > Cherry picked from commit a8486b9 Fixes: #4074 Change-Id: Idd767cf1793dba6a4f6fd52f00dfb6810bbe4a8d Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
mohit84
added a commit
to mohit84/glusterfs
that referenced
this issue
Nov 6, 2023
In ideal case the nlookup in kernel and fuse should be consistent but there is a case that fuse_direntplus_link would do nlookup++ and return fail due to that the counter is not consistent. To avoid a crash remove assertion and in case of value mismatch decrese the counter. > Fixes: gluster#4074 > Signed-off-by: ruanmeisi <ruan.meisi@zte.com.cn> > Reviwed on upstream link gluster#4081 > Cherry picked from commit a8486b9 Fixes: gluster#4074 Change-Id: Idd767cf1793dba6a4f6fd52f00dfb6810bbe4a8d Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
mohit84
added a commit
that referenced
this issue
Nov 9, 2023
…4257) In ideal case the nlookup in kernel and fuse should be consistent but there is a case that fuse_direntplus_link would do nlookup++ and return fail due to that the counter is not consistent. To avoid a crash remove assertion and in case of value mismatch decrese the counter. > Fixes: #4074 > Signed-off-by: ruanmeisi <ruan.meisi@zte.com.cn> > Reviwed on upstream link #4081 > Cherry picked from commit a8486b9 Fixes: #4074 Change-Id: Idd767cf1793dba6a4f6fd52f00dfb6810bbe4a8d Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem:
GlusterFS FUSE crash sometime,and can find Assertion failed message in logs, such as:
13732:[2023-01-11 06:04:43.481244] E [inode.c:767:inode_forget_atomic] (-->/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0xa073) [0x41f8073] -->/opt/lib/libglusterfs.so.0(inode_forget_with_unref+0x25) [0x4066755] -->/opt/lib/libglusterfs.so.0(+0x366dd) [0x40646dd] ) 0-: Assertion failed: inode_lookup >= nlookup
package-string: glusterfs 8.2
/opt/lib/libglusterfs.so.0(+0x27ccd)[0x4055ccd]
/opt/lib/libglusterfs.so.0(gf_print_trace+0x2e3)[0x405fc73]
/lib64/libc.so.6(+0x37400)[0x5d4b400]
/opt/lib/libglusterfs.so.0(+0x37535)[0x4065535]
/opt/lib/libglusterfs.so.0(inode_ref+0x23)[0x40659f3]
/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0x6628)[0x41f4628]
/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0xc8ab)[0x41fa8ab]
/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0x1e7d1)[0x420c7d1]
/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0x9e9c)[0x41f7e9c]
/opt/lib/glusterfs/8.2/xlator/mount/fuse.so(+0x22cac)[0x4210cac]
/lib64/libpthread.so.0(+0x817a)[0x580b17a]
/lib64/libc.so.6(clone+0x43)[0x5e10df3]
This issue is same as #2286 #2473 #2284
The exact command to reproduce the issue:
The full output of the command that failed:
Expected results:
Mandatory info:
- The output of the
gluster volume infocommand:- The output of the
gluster volume statuscommand:- The output of the
gluster volume healcommand:**- Provide logs present on following locations of client and server nodes -
/var/log/glusterfs/
**- Is there any crash ? Provide the backtrace and coredump
Additional info:
- The operating system / glusterfs version:
Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration
The text was updated successfully, but these errors were encountered: