Bug 885802 - NFS errors cause Citrix XenServer VM's to lose disks
Summary: NFS errors cause Citrix XenServer VM's to lose disks
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.3.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Vivek Agarwal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 902856
TreeView+ depends on / blocked
 
Reported: 2012-12-10 16:42 UTC by Gerald Brandt
Modified: 2016-02-18 00:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 902856 (view as bug list)
Environment:
Last Closed: 2013-08-28 11:13:42 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Gerald Brandt 2012-12-10 16:42:41 UTC 
Description of problem:
NFS log fills up with errors, load goes very high, and XenServer VM timeout on disk access, remounting them RO or crashing

Version-Release number of selected component (if applicable):
3.3.1

How reproducible:
Use NFS with XenServer and wait

Steps to Reproduce:
1.
2.
3.
  
Actual results:
log fills up with:
[2012-12-08 16:12:56.170509] E [nfs3.c:2163:nfs3_write_resume] 0-nfs-nfsv3: Unable to resolve FH: (192.168.20.13:943) NFS_RAID6_FO : 06799271-0ef4-4b7c-96ed-175c2c84994a
[2012-12-08 16:12:56.187355] W [nfs3-helpers.c:3389:nfs3_log_common_res] 0-nfs-nfsv3: XID: c81a4c3f, WRITE: NFS: 2(No such file or directory), POSIX: 14(Bad address)
[2012-12-08 16:12:57.197321] E [nfs3.c:2163:nfs3_write_resume] 0-nfs-nfsv3: Unable to resolve FH: (192.168.20.13:943) NFS_RAID6_FO : 06799271-0ef4-4b7c-96ed-175c2c84994a
[2012-12-08 16:12:57.197355] W [nfs3-helpers.c:3389:nfs3_log_common_res] 0-nfs-nfsv3: XID: 9e1b4c3f, WRITE: NFS: 2(No such file or directory), POSIX: 14(Bad address)


Expected results:
no errors, no loss of access

Additional info:
Comment 1 Gerald Brandt 2012-12-10 16:44:07 UTC 
This is on Ubuntu 12.04 LTS
Note You need to log in before you can comment on or make changes to this bug.