Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 493709

Summary: Kernel panic when dismount nfs4 FS
Product: Red Hat Enterprise Linux 4 Reporter: Marcus Alves Grando <marcus>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 4.6CC: jlayton, steved
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-10 12:10:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
panic picture none

Description Marcus Alves Grando 2009-04-02 18:59:41 UTC
Created attachment 337876 [details]
panic picture

Hello Jeff,

I've got an panic when tried to dismount a nfs4 area. I have a picture and now is installed diskdump to take all dump.

# uname -a
Linux plumculi.terra.com 2.6.9-67.0.20.ELsmp #1 SMP Thu Jun 26 08:30:18 EDT 2008 i686 i686 i386 GNU/Linux

Besides, I got a lot of messages in dmesg, see below:

nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 10
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 9
decode_getfattr: xdr error 5!
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 10
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 10
decode_getfattr: xdr error 10036!
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 9
decode_getfattr: xdr error 5!
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 9
decode_getfattr: xdr error 5!
decode_getfattr: xdr error 10036!
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 10
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 9
decode_getfattr: xdr error 5!
nfs4_decode_op_hdr: Server returned operation 10044 but we issued a request for 10
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!
decode_getfattr: xdr error 10036!

Picture is attched.

Regards

Comment 1 Jeff Layton 2009-04-02 19:43:54 UTC
Not sure right offhand about the xdr problems but the panic looks like a duplicate of bug 446396.

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

Comment 2 Jeff Layton 2009-04-02 19:47:05 UTC
My apologies. That one is a private bz so I can't add you. I'll leave this open for the time being. The panic you saw should be resolved in the coming 4.8 update.

Comment 3 Jeff Layton 2009-04-10 12:10:57 UTC

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