Comment 8 for bug 782925

I agree that this should be a separate bug, particularly since #344878 is not going to result in any changes.

In my experience, the ecryptfs-migrate-home script did not end elegantly, but instead stopped with a report of rsync errors. The encrypted directory was set up and worked, but that was not clear from the script output, nor was there any easy way to tell which files were not copied--or, in fact, that failure to copy long filenames was the cause of the error. All I saw was a cryptic numerical rsync error that "some files were not copied."

I would appreciate if the script were updated to better handle this error condition, and give the end-user some indication of whether it otherwise succeeded or failed. Alternately, it wouldn't hurt if there were some indication (other than searching for bug reports) in the instructions for the script that super-long filenames don't work in encrypted mode.