Difference between revisions of "File locks"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | Some app may use file locks for synchronization. Generally they will use flock or | + | Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and we should use the <code>--file-locks</code> option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping in theory. |
| − | + | Currently supported lock types are: | |
| − | + | * <code>flock()</code> locks | |
| − | * flock() locks | + | * POSIX (<code>fcntl</code>) locks |
| − | * | ||
| − | |||
| − | |||
| + | In future releases, we plan to also support: | ||
* file leases | * file leases | ||
* OFD locks | * OFD locks | ||
Revision as of 23:26, 20 September 2016
Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and we should use the --file-locks option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping in theory.
Currently supported lock types are:
flock()locks- POSIX (
fcntl) locks
In future releases, we plan to also support:
- file leases
- OFD locks
- mandatory locks