Changeset 862 for trunk/server/docs/manpages/vfs_crossrename.8
- Timestamp:
- May 13, 2014, 11:39:04 AM (11 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 860
- Property svn:mergeinfo changed
-
trunk/server/docs/manpages/vfs_crossrename.8
r752 r862 2 2 .\" Title: vfs_crossrename 3 3 .\" Author: [see the "AUTHOR" section] 4 .\" Generator: DocBook XSL Stylesheets v1.7 5.2<http://docbook.sf.net/>5 .\" Date: 10/29/20124 .\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/> 5 .\" Date: 09/18/2013 6 6 .\" Manual: System Administration tools 7 7 .\" Source: Samba 3.6 8 8 .\" Language: English 9 9 .\" 10 .TH "VFS_CROSSRENAME" "8" "10/29/2012" "Samba 3\&.6" "System Administration tools" 10 .TH "VFS_CROSSRENAME" "8" "09/18/2013" "Samba 3\&.6" "System Administration tools" 11 .\" ----------------------------------------------------------------- 12 .\" * Define some portability stuff 13 .\" ----------------------------------------------------------------- 14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 15 .\" http://bugs.debian.org/507673 16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html 17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 18 .ie \n(.g .ds Aq \(aq 19 .el .ds Aq ' 11 20 .\" ----------------------------------------------------------------- 12 21 .\" * set default formatting … … 32 41 The 33 42 vfs_crossrename 34 VFS module allows server side rename operations even if source and target are on different physical devices\&. A "move" in Explorer is usually a rename operation if it is inside of a single share or device\&. Usually such a rename operation returns NT_STATUS_NOT_SAME_DEVICE and the client has to move the file by manual copy and delete operations\&. If the rename by copy is done by the server this can be much more efficient\&. vfs_crossrename tries to do this server\-side cross\-device rename operation\&. There are however limitations that this module currently does not solve: 43 VFS module allows server side rename operations even if source and target are on different physical devices\&. A "move" in Explorer is usually a rename operation if it is inside of a single share or device\&. Usually such a rename operation returns NT_STATUS_NOT_SAME_DEVICE and the client has to move the file by manual copy and delete operations\&. If the rename by copy is done by the server this can be much more efficient\&. vfs_crossrename tries to do this server\-side cross\-device rename operation\&. 44 .PP 45 There are however limitations that this module currently does not solve: 35 46 .PP 36 47 .RS 4 37 38 the ACLs of files are not preserved 39 48 .PP 49 The ACLs of files are not preserved, 50 .RE 40 51 .PP 41 52 .RS 4 42 43 meta data in EAs are not preserved 44 53 .PP 54 meta data in EAs are not preserved, 55 .RE 45 56 .PP 46 57 .RS 4 47 48 renames of whole subdirectories cannot be done recursively, 49 in that case we still return STATUS_NOT_SAME_DEVICE and 50 let the client decide what to do 51 .RE 58 .PP 59 renames of whole subdirectories cannot be done recursively, in that case we still return STATUS_NOT_SAME_DEVICE and let the client decide what to do, 60 .RE 52 61 .PP 53 62 .RS 4 54 55 rename operations of huge files can cause hangs on the 56 client because clients expect a rename operation to 57 return fast 58 .RE 63 .PP 64 rename operations of huge files can cause hangs on the client because clients expect a rename operation to return fast\&. 65 .RE 59 66 .PP 60 67 This module is stackable\&.
Note:
See TracChangeset
for help on using the changeset viewer.