The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > OS Specific Forums > AIX
Google UNIX.COM


AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace.

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Lost+found morrish Shell Programming and Scripting 1 05-14-2008 08:01 PM
lost+found morrish UNIX for Advanced & Expert Users 3 04-23-2008 02:00 PM
what is lost+found dir? bok UNIX for Advanced & Expert Users 1 06-01-2005 12:09 PM
lost+found Prafulla UNIX for Advanced & Expert Users 4 03-31-2002 09:24 AM
Lost+found DPAI UNIX for Dummies Questions & Answers 6 02-19-2002 10:12 PM

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-29-2005
Registered User
 

Join Date: Jun 2005
Posts: 6
Exclamation Lost+Found is not available

Hi,

I have a AIX 4.3.3 running on IBM pseries server.
I have some jfs filesystems running on it.
I dont see Lost+Found directory in them.
Can anybody guide me why it is not available.

Cheers,
Vinod..
Reply With Quote
Forum Sponsor
  #2 (permalink)  
Old 06-30-2005
Bughunter Extraordinaire
 

Join Date: May 2005
Location: In the leftmost byte of /dev/kmem
Posts: 999
Maybe there was a small glitch in mkfs (that happens sometimes) or you have acidentally (with a mass-removal) deleted it.

'mkdir lost+found'

and the problem is solved.

bakunin
Reply With Quote
  #3 (permalink)  
Old 06-30-2005
Perderabo's Avatar
Unix Daemon
 

Join Date: Aug 2001
Location: Washington DC Area
Posts: 8,318
That is not enough to make a lost+found directory that can safely be used by fsck on a damaged filesystem. man mklost+found
Reply With Quote
  #4 (permalink)  
Old 07-04-2005
Bughunter Extraordinaire
 

Join Date: May 2005
Location: In the leftmost byte of /dev/kmem
Posts: 999
Perderabo, you're correct. It worked for me until now the way i have decribed it, though. Who knows, maybe it only seemed to work.

bakunin
Reply With Quote
  #5 (permalink)  
Old 07-04-2005
Perderabo's Avatar
Unix Daemon
 

Join Date: Aug 2001
Location: Washington DC Area
Posts: 8,318
You won't know until fsck attempts to connect some files there. And even if that works, it may have been dangerous. The issue is available space in the directory. If there is room for another {name, inode} pair, there is no problem. mklost+found expands the directory and since directories do not shrink, it stays expanded. Most versions of fsck discard the file if there is no room.

I heard a rumor that some recent bsd fsck versions will expand the lost+found directory if needed. If that's true, I hope that it builds a list of these unconnected inodes and waits until after the free list has been rebuilt. Allocating a block from a garbled free list is not wise. And I assume it must give up if the free list is empty.
Reply With Quote
Google UNIX.COM
Reply

Thread Tools
Display Modes




All times are GMT -7. The time now is 03:22 PM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited.
The UNIX and Linux Forums Content Copyright ©1993-2008 The CEP Blog All Rights Reserved -Ad Management by RedTyger Visit The Global Fact Book

Content Relevant URLs by vBSEO 3.2.0