Hot answers tagged

3

The sync (synchronous) setting is probably your bottleneck. You may consider trying to export with the async (asynchronous) flag, depending on your workload. Try benchmarking with it.


3

Network filesystems and databases can be a problematic combo, and at least InnoDB does not like NFS. From the MySQL documentation If reliability is a consideration for your data, do not configure InnoDB to use data files or log files on NFS volumes. Potential problems vary according to OS and version of NFS, and include such issues as lack of ...


3

NFSv4.2 does have a offload-copy operation which can do server-to-server copy without proxying data trough the client. Modern linux kernels (> 3.13?) supports that. I don't know about other servers. UPDATE By linux kernel 4.7 server side copy is not supported by linux servers https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/fs/nfsd/...


1

The "copy a file" operation is not a basic file-system operation such as read, write, open, close, and similar operations. See this page for a good explanation of the operations a filesystem has to support. And that's all file systems - whether it's ext4, btrfs, or nfsv4. Note that there's no way to know why a process opens file A, opens file B, reads ...


1

The error arise from the fact you are trying to sync into a directory which does not exist on the remote side. You have the following possibilities: first create the dir on the target directory issuing mkdir /mnt/myDir/var/www/dms/test (on the remote side), then issue your rsync command elaborating on that, if you need to transfer the entire /var/www ...



Only top voted, non community-wiki answers of a minimum length are eligible