Hi all,

after a crash of our SUN Server 220R on file system was corrupt
and I had run fsck getting a lost of files/dir's in the lost+found
of the file system loking like

drwxrwxr-x 2 lmxadmin DOS---- 512 Oct 31 21:04 #0007680
drwxrwxr-x 2 lammer DOS---- 512 Jan 29 09:29 #0035347
drwxrwxr-x 2 wohlfart DOS---- 512 Nov 2 15:59 #0045338
drwxrwxr-x 2 kaptur DOS---- 512 Jan 24 12:48 #0046080
drwxrwxr-x 2 hariskos DOS---- 512 Nov 15 09:23 #0046853
drwxrwxr-x 2 mantel DOS---- 1024 Jan 23 17:21 #0072324
drwxrwxr-x 2 kaptur DOS---- 29184 Jan 29 10:21 #0103786
drwxrwxr-x 2 mantel DOS---- 1024 Jan 23 16:55 #0103791
drwxrwxr-x 2 kaptur DOS---- 1024 Jan 24 14:09 #0167459

Is it possible to get the contents of the files. I tried to
read it in some way but as as they are directories, I wasn't
successful.

Any hints on getting the files back will be of great help.

DP

On Suns the size field of a directory is a multiple of 512 bytes. And the minimum number of links on a directory is 2. These directories fufill these requirements and I think that they are really directories. But, on unix, directories are files and you can read them if you have read permission. One program that reads directories is called "ls". But you can use other programs too. I suggest "od -c".

Have you looked inside these directories to see if your files are there?

When fsck finds a problem, I always rerun it to see if I get a clean result. Every now and then, a second fsck run finds additional errors. You might try that.

Also see this thread: Retrieval of deleted files.

The thing is , I go to the lost+found directory and whenever i give the command
ls #---<>----
It comes back to the home directory .... and shows the home directory too

I am confused ... How

DP

Files in the lost+found folders are usually files that has no inode for some valid reasons . Issue "file" command to determine if that file is a text file or something. And if you are sure that the file is part of what you need. Rename the file using the "mv" command outside the lost+found directory with respect to the type of file (e.g., mv <file> ~/<new filename>).

Thanks!

inquirer, there is no such thing as a file without an inode. Files (which have inodes) that are not listed in any directory are what gets reattached to lost+found and the name used is the inode number with a # in front of it.

DPAI, to most shells a # starts a comment. Try "ls \#0007680" or "ls ?0007680" or "ls *0007680".

It isn't going back to the home directory - some of the files that were lost WERE home directories. Just cd down to discover which ones were lost (do pwd to double check were you are).

When you ran fsck was it with the -y option?
If not, did you answer yes to all the questions?

Do you have a good backup? I don't know of a faster way to get the directories and files back then that unless you cd down to each home directory and move it back where it belongs. First you want to double check your hardware to insure you are not going to put them back on a bad disk.

"ls \#0007680" works . Thats great Per....

Yes hoghunter, i answered yes to all the questions . I mean thats the only way to get the partitions to load .

Or is there another way ..

Humor me

DP