Sometime Today, Amish Mehta assembled some asciibets to say:
Yesterday I was forced to hard reboot my Linux and when it passed through e2fsck it showed errors in lots of inodes. After going through fsck(where all I did is choose default answer) when I checked lost+found there were around 1200 files of size 4GB(HD space is 8GB). 'ls -l' doesnt show type of the file(it shows '?' question mark). Now if I try to remove those files it says 'Operation not permitted'. I also tried 'chmod 644' but that too fails. So now what
post a sample listing of the files. To figure out the file type, use the `file' command.
Also my harddisk is NOW showing 1GB free, as far as I knew it only had 200MB space left, does it mean I have lost the files? Can this happen? I was under impression that any unattached inodes go to lost+found. Also there can't be 800MB of data open at time of reboot
It is possible that a directory's inode was corrupted, so all files in there have gone to lost+found.
P.S. Kernel version is 2.2.17 and I am using the machine since 2 yrs and is reasonably stable.
I had a similar problem when I had 2.2.17, but was able to recover all my files - at least those that I wanted. In my case, the files showed correct attributes, only names had been changed. Files inside lost directories retained their original names (or I'd have had a hard time rebuilding those trees).
Philip