02-18-2010
The book "Design of the Unix Operating System" by Maurice J. Bach (1986) largely describes AT&T Unix System V release 2 (1984).
This book pre-dates modern journalling filesystems such as Veritas.
Maybe this is what you mean:
After say a power failure or a system crash it is possible on an old UFS filesystem to get the master block allocation table out of step with the inode table. The unix program "fsck" is designed to repair this situation and this program can re-create files in the "lost+found" directory without knowing the correct name of the file. In this case the inode table does not contain the name of the file but there are disc blocks allocated to that inode.
I this is not what you are looking for, please accurately type out the paragraph which contains the sentence.
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi i am nitin...
jus a new kid on the block... my query is...
does the concept of region invovle sharin of inodes wen the sticky it is set... eg... if two process share two text regions... wat actually happens
thank u (1 Reply)
Discussion started by: nitinsharma_ssn
1 Replies
2. Red Hat
hi,
can anyone please tell me where i can extract inode numbers and path associated with all file descriptors. i want these informations only. is there any system call or functions to get these things? i hav a RHEL 4. also /proc/pid/fd shows some file descriptor list. is that the proper path to... (1 Reply)
Discussion started by: sanjaykhuntia
1 Replies
3. UNIX for Dummies Questions & Answers
Dear Friend ,
what is incore inode ? and
what is difference between incore inode and inode ?????
sanjay (1 Reply)
Discussion started by: sanjaygoyan
1 Replies
4. Solaris
how can i see inode table information of a perticler inode.anybody knows pls tell me.
Than.Q (3 Replies)
Discussion started by: nag.mi2000
3 Replies
5. AIX
Hi Guys,
I have this filesystem got big with inode:
/dev/hd4 3670016 183664 95% 63705 58% /var
I don't know why the system doesn't give alerts on this FS although it's 95% and why the inode is 58%.
Any comments will be highly appreciated.
Thanks,
itik (1 Reply)
Discussion started by: itik
1 Replies
6. Solaris
Hi,
I have a problem one of the server file system cross the limitation
MountPoint / is 8% with 899.49MB free crossing threshold of 10% free
out put please help how to resolve this
dev/vx/dsk/bootdg/rootvol
9.8G 8.8G 956M 91% /
/devices ... (3 Replies)
Discussion started by: sriniva0
3 Replies
7. Solaris
Dear,
How can i check inode information in my Solaris box?
With Regards,
Mjoshi (4 Replies)
Discussion started by: mjoshi87
4 Replies
8. Red Hat
Hi, I am having similar issue showing filesystem 100% even after deleting the files. I understood the issue after going through this chain. But i can not restart the processes being oracle database. Is there way like mounting filesytem with specific options would avoid happening this issue.
How... (0 Replies)
Discussion started by: prashant185
0 Replies
clri(1M) clri(1M)
NAME
clri - clear inode
SYNOPSIS
special i-number ...
DESCRIPTION
The command clears the inode i-number by filling it with zeros. special must be a special file name referring to a device containing a
file system. For proper results, special should not be mounted (see WARNINGS below). After is executed, all blocks in the affected file
show up as "missing" in an of special (see fsck(1M)). This command should only be used in emergencies.
Read and write permission is required on the specified special device. The inode becomes allocatable.
WARNINGS
The primary purpose of this command is to remove a file that for some reason does not appear in any directory. If it is used to clear an
inode that does appear in a directory, care should be taken to locate the entry and remove it. Otherwise, when the inode is reallocated to
some new file, the old entry in the directory will still point to that file. At that point, removing the old entry destroys the new file,
causing the new entry to point to an unallocated inode, so the whole cycle is likely to be repeated again.
If the file system is mounted, is likely to be ineffective.
DEPENDENCIES
operates only on file systems of type
SEE ALSO
fsck(1M), fsdb(1M), ncheck(1M).
STANDARDS CONFORMANCE
clri: SVID2, SVID3
clri(1M)