The original article has expired from my newsreader, so this one won't
be linked properly... However, I just did some experimentation on a
filesystem, and I never saw these results mentioned.

In article <MPG.19525e71b3442e07989699@10.1.1.10>, Jeffrey C. Drywater
says...
> You were right, the man page for fsck_ufs does contain the text
> regarding the lost+found directory, however still having no luck.
>
> The following command...
>
> fsck -F ufs -y /dev/dsk/c0t1d0s0
> ...fails to recreate the lost+found directory. The system is running
> fine and I think at this point I'm just going to leave it as is. Worst
> case, I'll recreate the filesystem and restore the data.
In my testing with a Solaris 8 02/02 system and a UFS filesystem with a
removed lost+found, fsck will *not* create a lost+found and properly
relink files *if* inode 3 is occupied.

If inode 3 is available and files need to be reconnected, the fsck will
create the directory.

It won't create it in either case if it doesn't need to reconnect
anything.

My tests were done by creating a directory with files, then removing
that directory with 'crli', then running fsck.

--
Darren Dunham [email]ddunham@taos.com[/email]
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >