lost+found questions

[Olivier Decorse]

hello, my OS release is 10.20 and my questions are :
1) what information do i find in the lost+found directory : inodes ? files ?
2) How can i know the file that match with this information ?
3) i've got a message like : "Rebuild structural files - Lost+Found is full - Sorry cannot reconnect clear". Does it means that the lost+found directory have a quota (for information : the partitions is not full : more than 50Mbytes free !),
4) Does we need to do free space on lost+found, shutdown and run fsck in runlevel 0 to really clean the file systems ?
5) files in /lost+found are special files, like (cmd 'ls -l') : "crw-rw-rw- 1 root sys 157 0x00001c Oct 12 1999 161 " How can i know the file that could not be repeared ?
6) i know that fsck is run before all file systems are mount, but is there a file that contains all message that fsck produce ?
7) an empty lost+found directory return 0 with a 'du -s lots+found' directory, except /stand/lost+foud : 16. Why ?
8) where can i found documentation about maintaining directory lost+found ?

Thank's in advance for all response.
Olivier.

[Andreas Voss]

Hi,

files in lost+found are those ones which have lost their reference (not knowing where they were located).
So the only chance to know where the files have been located is guessing :(

For more information see 'man mklost+found'

Regards

[Maureen Gunkel]

Decorse,
I know this sounds simplistic, but all I have ever done is clear out the lost+found directory when needed. It is very difficult (at best) to find out what they are, where they belong, etc. And if they're lost, they're lost :-(. Hope that this helps,
Mo

[James R. Ferguson]

Decorse:

The lost+found directory is also used during vxfs 'fsadm' defragmentation. From the fsadm man pages:

fsadm uses the file .fsadm in the lost+found directory as a lock file. When fsadm is invoked, it opens the file lost+found/.fsadm in the root of the file system specified by mount_point. If the file does not exist, it is created. The fcntl(2) system call is used to obtain a write lock on the file. If the write lock fails, fsadm will assume that another fsadm is running and will fail. fsadm will report the process ID of the process holding the write lock on the .fsadm file.

...JRF...

[Olivier Decorse]

Closed.