Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How did you "move a lot of data?" (I.e., which command(s) did you use?)
What you're seeing in the ls output is a "clobbered" directory file, which should not have happened regardless of what you did. I had that happen (to a single file) when I closed the wrong terminal window before the copy finished, but was able to recover by going to a "root" terminal window and using chown there, but, in my case, the file sizes were correctly set in the directory file, so only the ownership needed resetting.
You could try a file recovery tool like foremost or testdisk.
nb. i just used 'mv'. Something like mv dir/ /dir2 (move dir into dir2), where dir was at least 20 gb...
ok, tried testdisk. it reports no errors, when fetching the file list in testdisk, it gives back a list as it should be, even with the right user id (1000). but doing an ls, gives the same result. it seems as if only the 'root' directory file of the hd is bad. assume i've mounted the hd on /mnt, ls /mnt -l gives back the result in my first post, doing a ls /mnt/video -l gives a 'no such file or directory'...
if anyone could give me a kick in the right direction, i would be very grateful!
well.... i've managed to f*ck up another hd too... one advantage is that i now know what i did wrong...
the hd was mounted on /data/ I wanted to reset all permissions on the hd to 644 (for a start, wanted to do chmod +X later). This is what i did:
chmod -R 644 /data
i got an Perission denied warning, and after that, the same nice ls output:
?--------- ? ? ? ? ? data/docs
?--------- ? ? ? ? ? data/downloads
?--------- ? ? ? ? ? data/dump
so it wasn't the moving, but the chmod who damaged the directory file...
btw. note that a directory in the 'root' dir of the mounted disk looks like data/docs instead of docs.
Was that a sudo chmod -R 644 /data or did you neglect the sudo? (Unless you'd logged in as "root," which is, normally, a locked account which you cannot use. It can be unlocked, but doing so is "discouraged" by the Ubuntu developers.)