	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.6

rsync corrupts files

Asked by nuke3dd in rSync Backup Utility, Bourne-Again Shell (bash)

Tags: rsync linux bash checksum corruption mdadm raid

I've used rsync to copy around 300GB of data in the form of small text files, large binary executables/videos, word documents etc. Source and target are both on different md raid1 devices on the same machine. The rsync command was:

# rsync -aHxv /mnt/src/ /mnt/dst/

All seemed to work well, but then I did a quick

# diff -r /mnt/src /mnt/dst

Which showed some files that differed. Around 8-10 files, a far as I can remember. A cmp -l on such a file would always return a single byte difference, and it was always the value in the old file incremented by one:

# cmp -l /mnt/src/file.exe /mnt/dst/file.exe
82778 24 25

This seems to be quite systematic. I still have the source files, so now I did a

# rsync -caHxv /mnt/src/ /mnt/dst/

and this effectively re-transfers all the corrupted files, this time without corruption.

Rsync is supposed to check the checksum of transfered files, so how is this corruption even possible?

Is there something I have to take care of when transferring large volumes of data locally with rsync? How can I be sure that this doesn't happen again (without using -c, because this takes ages)?

View the Solution FREE for 30 Days

20091118-EE-VQP-93 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. ai_ja_nai29,250
2. woolmilkp...17,050
3. jmcse14,050
4. martin_2...3,500
5. rindi3,250
6. noxcho3,050
7. MiLLeNNiuM2,800
8. Mysidia2,500
8. fosiul012,500
10. johnnash...2,300
11. arober112,288
12. Mikal6132,000
12. oBdA2,000
12. farhankazi2,000
12. shalomc2,000
12. AmazingT...2,000
12. torimar2,000
12. bdb1122,000
12. Computer...2,000
12. Roachy1...2,000
12. micalkin2,000
12. TCB12,000
12. amnonnes2,000
12. Mestha2,000
12. hathehariken2,000
12. darrickhar...2,000

1. ai_ja_nai35,850
2. woolmilkp...18,050
3. Tintin16,522
4. rindi8,650
5. kode998,000
6. ravenpl7,950
7. gurutc7,836
8. SysExpert7,140
9. leew5,875
10. noxcho5,800
11. ahoffmann5,250
12. Mr-Madc...5,050
13. svs5,000
14. fosiul014,500
15. Mehuge4,180
16. jmcse14,050
17. DocGyver4,000
17. Callandor4,000
19. dovidmichel3,500
19. martin_2...3,500
21. robocat3,400
22. yuzh3,250
22. omarfarid3,250
24. agriesser3,000
25. eoinosullivan2,900

rsync corrupts files

Asked by nuke3dd in rSync Backup Utility, Bourne-Again Shell (bash)

Tags: rsync linux bash checksum corruption mdadm raid

About this solution