I'm working on a RHEL6 bug where the client gets stuck in a WRITE,BAD_STATEID loop forever, and it looks like what happens is the write continually picks a delegated write lock stateid in nfs4_select_rw_stateid() for the write which never gets cleaned up in the state machine because a previous OPEN during recovery had a BAD_SEQID come in which dropped the state_owner. Does it make sense to try to find lock stateids and set NFS_LOCK_LOST if we're going to drop the state_owner? It may be entirely impossible to reproduce the problem upstream, but I figured I'd ask while I try.. Ben -- 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
