how windows or linux resolve file rename/move/copy
I wonder how linux and windows resolve file rename or file move (drag and drop) at low level?
In java we have File.move but I don't know how it really works ?
In apache common we have FileUtils.moveFile
What "move file" does mean in linux and windows? Does systems put in memory file when moving/rename file then create new file and delete old one ?
java linux powershell nio apache-commons
asked Nov 19 '18 at 9:33
beebee
4418
add a comment |
I wonder how linux and windows resolve file rename or file move (drag and drop) at low level?
In java we have File.move but I don't know how it really works ?
In apache common we have FileUtils.moveFile
What "move file" does mean in linux and windows? Does systems put in memory file when moving/rename file then create new file and delete old one ?
java linux powershell nio apache-commons
asked Nov 19 '18 at 9:33
beebee
4418
2
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
Abstractions my friend! Java dispatches a file-system agnosticmove()instruction to a platform-specificFileSystemProviderwhich then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for amoveoperation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down
– Mathias R. Jessen
Nov 19 '18 at 9:57
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35
add a comment |
I wonder how linux and windows resolve file rename or file move (drag and drop) at low level?
In java we have File.move but I don't know how it really works ?
In apache common we have FileUtils.moveFile
What "move file" does mean in linux and windows? Does systems put in memory file when moving/rename file then create new file and delete old one ?
java linux powershell nio apache-commons
asked Nov 19 '18 at 9:33
beebee
4418
I wonder how linux and windows resolve file rename or file move (drag and drop) at low level?
In java we have File.move but I don't know how it really works ?
In apache common we have FileUtils.moveFile
What "move file" does mean in linux and windows? Does systems put in memory file when moving/rename file then create new file and delete old one ?
java linux powershell nio apache-commons
java linux powershell nio apache-commons
asked Nov 19 '18 at 9:33
beebee
4418
asked Nov 19 '18 at 9:33
beebee
4418
asked Nov 19 '18 at 9:33
beebee
4418
asked Nov 19 '18 at 9:33
beebee
4418
asked Nov 19 '18 at 9:33
beebee
4418
4418
2
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
Abstractions my friend! Java dispatches a file-system agnosticmove()instruction to a platform-specificFileSystemProviderwhich then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for amoveoperation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down
– Mathias R. Jessen
Nov 19 '18 at 9:57
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35
add a comment |
2
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
Abstractions my friend! Java dispatches a file-system agnosticmove()instruction to a platform-specificFileSystemProviderwhich then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for amoveoperation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down
– Mathias R. Jessen
Nov 19 '18 at 9:57
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35
2
2
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
Abstractions my friend! Java dispatches a file-system agnostic
move() instruction to a platform-specific FileSystemProvider which then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for a move operation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down– Mathias R. Jessen
Nov 19 '18 at 9:57
Abstractions my friend! Java dispatches a file-system agnostic
move() instruction to a platform-specific FileSystemProvider which then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for a move operation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down– Mathias R. Jessen
Nov 19 '18 at 9:57
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35
add a comment |
1 Answer
1
active
oldest
votes
Copy and rename are different operations.
- Copy produces a new file. It is done by copying bytes1; e.g. open files and use read / write syscalls to copy the bytes.
- Rename changes the pathname for an existing file. It is done by a syscall that changes the metadata for a file and the source and destination directories.
There are a couple of wrinkles.
Rename (on Linux) only works within a file system. You cannot rename a file to a pathname in a different file system.
There is no "move" syscall in Linux / POSIX libraries. So (for example) the
mvcommand on Linux will either rename the file, or make a copy (and delete the original), depending on where source and destination are.Copying a file could be implemented in a lazy way using copy-on-write. For example, the "btrfs" supports copy-on-write, and it is possible that this functionality could be exposed to the application.
In a Java application, copy is implemented by copying the bytes of the file, and rename is implemented by calling the OS-provide rename syscall (see above). The move verb is typically a hybrid of copy and move as above.
That is the simple version. In practice, performance also depends on how the file system metadata is organized and stored, and on the various "tricks" that the OS uses to speed things up; e.g. caching metadata and file data in memory, read ahead / write behind, using "metadata transaction logs" to speed up metadata operations. And there are hardware-basewd tuning tricks like putting the metadata onto storage media with higher IOPs per second than the data. (This is particularly necessary if you are dealing with file systems with tens of millions of files ...)
1 - Actually, opening a file and creating a new one both involve reading and writing metadata, but this only happens once per file copied. By contrast, if you are copying a file, you typically have to write (and possibly read) all disk blocks for the file. For a large file, the reads and writes will dominate the metadata operations.
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371739%2fhow-windows-or-linux-resolve-file-rename-move-copy%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Copy and rename are different operations.
- Copy produces a new file. It is done by copying bytes1; e.g. open files and use read / write syscalls to copy the bytes.
- Rename changes the pathname for an existing file. It is done by a syscall that changes the metadata for a file and the source and destination directories.
There are a couple of wrinkles.
Rename (on Linux) only works within a file system. You cannot rename a file to a pathname in a different file system.
There is no "move" syscall in Linux / POSIX libraries. So (for example) the
mvcommand on Linux will either rename the file, or make a copy (and delete the original), depending on where source and destination are.Copying a file could be implemented in a lazy way using copy-on-write. For example, the "btrfs" supports copy-on-write, and it is possible that this functionality could be exposed to the application.
In a Java application, copy is implemented by copying the bytes of the file, and rename is implemented by calling the OS-provide rename syscall (see above). The move verb is typically a hybrid of copy and move as above.
That is the simple version. In practice, performance also depends on how the file system metadata is organized and stored, and on the various "tricks" that the OS uses to speed things up; e.g. caching metadata and file data in memory, read ahead / write behind, using "metadata transaction logs" to speed up metadata operations. And there are hardware-basewd tuning tricks like putting the metadata onto storage media with higher IOPs per second than the data. (This is particularly necessary if you are dealing with file systems with tens of millions of files ...)
1 - Actually, opening a file and creating a new one both involve reading and writing metadata, but this only happens once per file copied. By contrast, if you are copying a file, you typically have to write (and possibly read) all disk blocks for the file. For a large file, the reads and writes will dominate the metadata operations.
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
add a comment |
Copy and rename are different operations.
- Copy produces a new file. It is done by copying bytes1; e.g. open files and use read / write syscalls to copy the bytes.
- Rename changes the pathname for an existing file. It is done by a syscall that changes the metadata for a file and the source and destination directories.
There are a couple of wrinkles.
Rename (on Linux) only works within a file system. You cannot rename a file to a pathname in a different file system.
There is no "move" syscall in Linux / POSIX libraries. So (for example) the
mvcommand on Linux will either rename the file, or make a copy (and delete the original), depending on where source and destination are.Copying a file could be implemented in a lazy way using copy-on-write. For example, the "btrfs" supports copy-on-write, and it is possible that this functionality could be exposed to the application.
In a Java application, copy is implemented by copying the bytes of the file, and rename is implemented by calling the OS-provide rename syscall (see above). The move verb is typically a hybrid of copy and move as above.
That is the simple version. In practice, performance also depends on how the file system metadata is organized and stored, and on the various "tricks" that the OS uses to speed things up; e.g. caching metadata and file data in memory, read ahead / write behind, using "metadata transaction logs" to speed up metadata operations. And there are hardware-basewd tuning tricks like putting the metadata onto storage media with higher IOPs per second than the data. (This is particularly necessary if you are dealing with file systems with tens of millions of files ...)
1 - Actually, opening a file and creating a new one both involve reading and writing metadata, but this only happens once per file copied. By contrast, if you are copying a file, you typically have to write (and possibly read) all disk blocks for the file. For a large file, the reads and writes will dominate the metadata operations.
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
add a comment |
Copy and rename are different operations.
- Copy produces a new file. It is done by copying bytes1; e.g. open files and use read / write syscalls to copy the bytes.
- Rename changes the pathname for an existing file. It is done by a syscall that changes the metadata for a file and the source and destination directories.
There are a couple of wrinkles.
Rename (on Linux) only works within a file system. You cannot rename a file to a pathname in a different file system.
There is no "move" syscall in Linux / POSIX libraries. So (for example) the
mvcommand on Linux will either rename the file, or make a copy (and delete the original), depending on where source and destination are.Copying a file could be implemented in a lazy way using copy-on-write. For example, the "btrfs" supports copy-on-write, and it is possible that this functionality could be exposed to the application.
In a Java application, copy is implemented by copying the bytes of the file, and rename is implemented by calling the OS-provide rename syscall (see above). The move verb is typically a hybrid of copy and move as above.
That is the simple version. In practice, performance also depends on how the file system metadata is organized and stored, and on the various "tricks" that the OS uses to speed things up; e.g. caching metadata and file data in memory, read ahead / write behind, using "metadata transaction logs" to speed up metadata operations. And there are hardware-basewd tuning tricks like putting the metadata onto storage media with higher IOPs per second than the data. (This is particularly necessary if you are dealing with file systems with tens of millions of files ...)
1 - Actually, opening a file and creating a new one both involve reading and writing metadata, but this only happens once per file copied. By contrast, if you are copying a file, you typically have to write (and possibly read) all disk blocks for the file. For a large file, the reads and writes will dominate the metadata operations.
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
Copy and rename are different operations.
- Copy produces a new file. It is done by copying bytes1; e.g. open files and use read / write syscalls to copy the bytes.
- Rename changes the pathname for an existing file. It is done by a syscall that changes the metadata for a file and the source and destination directories.
There are a couple of wrinkles.
Rename (on Linux) only works within a file system. You cannot rename a file to a pathname in a different file system.
There is no "move" syscall in Linux / POSIX libraries. So (for example) the
mvcommand on Linux will either rename the file, or make a copy (and delete the original), depending on where source and destination are.Copying a file could be implemented in a lazy way using copy-on-write. For example, the "btrfs" supports copy-on-write, and it is possible that this functionality could be exposed to the application.
In a Java application, copy is implemented by copying the bytes of the file, and rename is implemented by calling the OS-provide rename syscall (see above). The move verb is typically a hybrid of copy and move as above.
That is the simple version. In practice, performance also depends on how the file system metadata is organized and stored, and on the various "tricks" that the OS uses to speed things up; e.g. caching metadata and file data in memory, read ahead / write behind, using "metadata transaction logs" to speed up metadata operations. And there are hardware-basewd tuning tricks like putting the metadata onto storage media with higher IOPs per second than the data. (This is particularly necessary if you are dealing with file systems with tens of millions of files ...)
1 - Actually, opening a file and creating a new one both involve reading and writing metadata, but this only happens once per file copied. By contrast, if you are copying a file, you typically have to write (and possibly read) all disk blocks for the file. For a large file, the reads and writes will dominate the metadata operations.
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
edited Nov 19 '18 at 14:38
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
answered Nov 19 '18 at 14:18
Stephen CStephen C
517k70568925
517k70568925
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
add a comment |
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
thank you, for copy this is OK to understand it put bytes in memory then create new file, but what about "move" you said : no move on linux because everything is file it almost always rename it (metadata) but what about windows, if in java we call move() does it try to rename ? or it do copy-on-write? im not sure windows is able to rename only metadata to move file from c:/x/x/x/c.pdf to c:/y/y/y.pdf just renaming metadata (in same filesystem) and however when I drag and drop it seems faster than copy+paste or im dreaming
– bee
Nov 20 '18 at 10:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
I don't know for sure, but I think it will be the same. Cross-filesystem renames are not possible. Drag and drop is a "move". Copy and paste is a "copy".
– Stephen C
Nov 20 '18 at 15:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371739%2fhow-windows-or-linux-resolve-file-rename-move-copy%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
you should clearly read about low level things in a file system resp. operating system, buffers and all the fancy memory management things. It's pretty interesting
– AKSW
Nov 19 '18 at 9:34
Abstractions my friend! Java dispatches a file-system agnostic
move()instruction to a platform-specificFileSystemProviderwhich then figures out which OS-level API to call, after which the OS figures out what kind of file system the given file resides on and then figures out the correct instruction for amoveoperation on the filesystem, which then in turn figures out how to move the bytes around on disk (usually just updates references in a file system table). IOW It's turtles all the way down– Mathias R. Jessen
Nov 19 '18 at 9:57
@AKSW thank you, you should share link about that :)? you speak about buffers/memory mangement : I still not know if I ask more work to my disk if I first read bytes from file then save it another place or it is better just move file, does thes both solicite my disk identically or ?
– bee
Nov 19 '18 at 10:33
@MathiasR.Jessen thank you, that is my question i want know how system manage it, to understand if it is faster to move() OR read file bytes then create new file in another place, how system windows/linux manage buffers, does this solicit identically disk
– bee
Nov 19 '18 at 10:35