Additional Info





I think there is a world market for maybe five computers. (Thomas Watson, Chairman of IBM, 1943)





This post tagged:

FAQ








Share

Unix, Xenix and ODT General FAQ

This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open This is an old article about SCO Unix and is only left here for historical purposes. There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.

Why can't fsck find my lost+found directory (Old Sco Unix)?

Because you don't have one. It's possible someone deleted it, but the more likely cause is that you didn't use mkdev fs to create it.

Linux has "mklost+found".

One of the things that fsck looks for is inodes which are marked as used (i.e. not in the free list) but do not have a directory entry pointing to them. fsck will ask if you wish to reconnect these; if you say yes, it will try to create a file entry in the /lost+found directory on that filesystem. If there is no free space in /lost+found, it is not safe to expand it because the rest of the filesystem may still be corrupt; for information on this one, see below. If there is not /lost+found directory, fsck will tell you that it can't reconnect the file and the data in that file will be lost.



Got something to add? Send me email.





(OLDER) <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> (SCO Unix) Why can't fsck find my lost+found directory?



Increase ad revenue 50-250% with Ezoic

Kerio Samepage


Have you tried Searching this site?

Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us