Did I just lose my mp3s with a bad mv command?
I just woke up, and was checking out some mp3s that got downloaded last night. There were some that had the filename format of ## song title.mp3 and others that had the filename format of ##-artist-song_title.mp3 (no spaces). So I wanted to move the ones with spaces to a separate directory. But I wasn't paying attention and issued the following command:
Code:
mv ./* *.mp3 albums/magnum_force The fs is ext3 (if that has any significance). |
Have you tried performing a search for them first? Maybe with a find or locate command?
|
Quote:
Yes sir. Actually one of the first things I did was run updatedb then locate mp3 |less My findings so far indicate that file recovery seems possible with ext2, but not ext3. The following is something I found at http://batleth.sapienti-sat.org/proj.../ext3-faq.html Quote:
|
I don't know what command you executed there, but it looks like it did some nastiness :)
You may want to add a line like: alias mv mv -i to your .bashrc or .profile or whatnot, to cause mv to prompt you for stuff like that in the future. Boy, right here is a great answer for all those who ask "why not run as root all the time?" |
Quote:
Actually what happened was the mp3s and sub-directories that disappeared got moved to albums/magnum_force (luckily). Much thanks goes to realnowhereman over at DevShed. He put in a great effort to find out what really happened. Also, I already went into .bashrc and made an alias for mv but included the --verbose option ;) |
All times are GMT -5. The time now is 10:20 AM. |