02-18-2010
reply
you are right what you said...
and that is naturally generally happens...
but in book design of unix os by maurica bach there it is written...
there are some exceptional cases also where free inode number is less than remembered inode.....which seems impossible...
just let me know if u can find any such cases..
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
LEARN ABOUT DEBIAN
matchpathcon_checkmatches
matchpathcon_checkmatches(3) SELinux API documentation matchpathcon_checkmatches(3)
NAME
matchpathcon_checkmatches, matchpathcon_filespec_add, matchpathcon_filespec_destroy, matchpathcon_filespec_eval - check and report whether
any specification index has no matches with any inode. Maintenance and statistics on inode associations.
SYNOPSIS
#include <selinux/selinux.h>
void matchpathcon_checkmatches(char *str);
int matchpathcon_filespec_add(ino_t ino, int specind, const char *file);
void matchpathcon_filespec_destroy(void);
void matchpathcon_filespec_eval(void);
DESCRIPTION
matchpathcon_checkmatches checks whether any specification has no matches and reports them. The str argument is used as a prefix for any
warning messages.
matchpathcon_filespec_add maintains an association between an inode ino and a specification index specind, and checks whether a conflicting
specification is already associated with the same inode (e.g. due to multiple hard links). If so, then it uses the latter of the two speci-
fications based on their order in the file context configuration. Returns the specification index used or -1 on error.
matchpathcon_filespec_destroy destroys any inode associations that have been added, e.g. to restart for a new filesystem.
matchpathcon_filespec_eval displays statistics on the hash table usage for the inode associations.
RETURN VALUE
Returns zero on success or -1 otherwise.
SEE ALSO
selinux(8), matchpathcon(3), matchpathcon_index(3), freecon(3), setfilecon(3), setfscreatecon(3)
sds@tycho.nsa.gov 21 November 2009 matchpathcon_checkmatches(3)