Hi folks, As far as I can tell, receiving a BAD_STATEID on an IO operation on a delegated stateid when there was a local lock acquired for this IO is unrecoverable — leads to EIO. Codewise, stateid recovery sees that it has a local lock and marks it lost and retry of the IO operation returns the EIO. Is the reason for seizing the IO is that if the server for some reason revoked this stateid then there is no guarantee about the locks and thus doing any IO. This also applies to both 4.0 and 4.1 code as far as I can tell. Can somebody confirm or tell me if this is wrong? Thank you. -- 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
