Changes

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.

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.

Supported lock types are

Currently supported lock types are:

 

* <code>flock()</code> locks

* flock() locks

* POSIX (<code>fcntl</code>) locks

* posix (fcntl) locks

 

* file leases

* file leases

* OFD locks

* OFD locks