Hello, A couple of weeks agoo we upgraded our Netapp filer to 8.1.1RC1. We have always had trouble with NFS and state id's. Resulting in hanging clients. Some bugs were fixed in 8.1.1 but still trouble. Now we have the following errors in our client messages file, after a hang. What does this : NFS: "v4 server srv returned a bad sequence-id error!" means ? ---- Aug 17 14:08:23 tudxxxxxx kernel: [622014.866818] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:23 tudxxxxxx kernel: [622014.872143] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112dcc20! Aug 17 14:08:23 tudxxxxxx kernel: [622014.872871] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112dcc20! Aug 17 14:08:23 tudxxxxxx kernel: [622015.170658] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8801112e6820! Aug 17 14:08:23 tudxxxxxx kernel: [622015.278260] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:23 tudxxxxxx kernel: [622015.651868] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:24 tudxxxxxx kernel: [622016.051741] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:25 tudxxxxxx kernel: [622017.155713] NFS: v4 server srvxxx returned a bad sequence-id error! Aug 17 14:08:25 tudxxxxxx kernel: [622017.346225] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620! Aug 17 14:08:25 tudxxxxxx kernel: [622017.349781] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620! Aug 17 14:08:25 tudxxxxxx kernel: [622017.350840] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff8800bcf39620! -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
