Skip to contentSkip to conversation

nfs4 locks: What happens when a lease can't get renewed?

DISCUSSION Nils Goroll 2 participants 2 messages Jun 11, 2010 – Jun 17, 2010 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi,

I wonder what happens if a lock on nfs4 has been acquired by an application (for instance, using fcntl(fd, F_SETLK, F_WRLCK)) and the lock can't be RENEWed, for instance due to a network outage preventing communication between the client and the server.

I would have thought that some notification mechanism was useful, for instance my means of delivery of a signal as set using F_SETOWN / F_SETSIG for leases.

I would highly appreciate helpful pointers should this question have already been discussed of if there exists any other helpful documentation on it.

Thank you,

Nils

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi,

I am reposting my question because I feel it is quite substantial. IMHO, some mechanism to ensure data integrity is needed for "lost locks".

Quoted 20 lines · Nils Goroll

Hi,

I wonder what happens if a lock on nfs4 has been acquired by an application (for instance, using fcntl(fd, F_SETLK, F_WRLCK)) and the lock can't be RENEWed, for instance due to a network outage preventing communication between the client and the server.

I would have thought that some notification mechanism was useful, for instance my means of delivery of a signal as set using F_SETOWN / F_SETSIG for leases.

I would highly appreciate helpful pointers should this question have already been discussed of if there exists any other helpful documentation on it.

Thank you,

Nils
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html