Hi, My nfs.log is filled with this:
[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) Again. All my XenServer based VM's lost their drives. I'm not very happy. This started being an issue at the beginning of November with 3.3.0, and has continued. It may be load based. Gerald _______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
