Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Ok, it's probably my fault, but hear me out. I was backing up some important files (chat logs, email, etc.) to my 2nd computer's share folder which I had mounted using smb4k. For the chat logs I copied and pasted using ctrl+c and ctrl+v like I normally do. For my email folder, I decided to use the "copy to" function in KDE and browsed to smb4k > computer_name > share_folder and I saw "copy here" right above the share folder name. I took that as meaning "copy my files to the share folder", which apparently is wrong. Also, turns out that I accidently selected "move to" instead of "copy to". So, it tried to move my files to no particular directory on my second computer and it didn't give me any error messages about it. It just deleted all my email files! I do have a semi-recent backup, but it's from maybe 2 weeks ago, not that I've gotten many important emails recently anyway...
I'm using reiserfs so there aren't really any easy ways to recover the files it seems (unless anyone knows one?) but I am upset that KDE didn't say something like "hey, you can't move files here, stupid!" I dunno, I just wanted to vent more than anything, but any suggestions on getting my files back would be appriciated.
Sorry, I cannot help you get your files back, but this is one of the problems associated with using KDE or any other GUI to do important moves / copies / backups.
Having made a similar mistake I always use the command line now! That way you'll get to see the error messages and know your command has not behaved as expected.