Linux

47583 readers

832 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Does cp -v print out the file name when it starts copying it or when it's done? (lemmy.ml)

submitted 10 months ago* (last edited 10 months ago) by HiddenLayer5@lemmy.ml to c/linux@lemmy.ml

13 comments fedilink hide all child comments

So if I had a cp -v operation fail, is the last file name it printed out the last successful file copy, or is it the failed partially copied file? If you had to ensure all files are copied correctly without overwriting anything, would deleting the last filename that was printed from the destination folder delete the partially copied file that the operation failed on?

you are viewing a single comment's thread
view the rest of the comments

[–] SpaceCadet@feddit.nl 31 points 10 months ago* (last edited 10 months ago) (2 children)

Just use rsync -va

NO STOP!

The default quick check algorithm of rsync is not safe for this. It only checks filesize and modification time to determine if files are equal. After a b0rked copy, these are not to be trusted.

You should add the -c flag so that files are properly checksummed, unfortunately if you have slow storage on either end, this often negates the speed advantage of rsync.

For example, consider this example:

mkdir source
mkdir destination
echo "hello" > source/file.txt
echo "world" > destination/file.txt
touch -r source/file.txt destination/file.txt
rsync -avh source/ destination/
cat source/file.txt
cat destination/file.txt

Contrary to what you might expect, the rsync command copies nothing and the output at the end will show:

hello
world

If you change the rsync command in the example above to rsync -c -avh source/ destination/, it will work as expected.

[–] taladar@sh.itjust.works 1 points 10 months ago

True if the initial state is unknown but if you do your initial copy and all the later syncs with rsync it is not really necessary since rsync puts the partial files in a temporary location (there are same parameters to control the details of that too).

[–] damium@programming.dev 1 points 10 months ago

My memory of the cp command is that attributes such as file times were transferred at the last step. I think this would make rsync safe in most situations where a system crash wasn't involved.