03-26-2014
It is possible that the application is using "fstat*" system calls to get inode numbers. I can prepare a new version of the DTrace script tomorrow, if you are interested.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When is a file "accessed" according to UNIX? For example: gzipping a file will not change the access time. (1 Reply)
Discussion started by: dangral
1 Replies
2. Ubuntu
Hi,
If inodes need to be 3-4 times greater than fd.file-max. Can you modify the current inode in the filesystem? Can you modify it on the fly? Or only in the creation of FS.
I'm using redhat ent 4.
Thank you for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies
3. Filesystems, Disks and Memory
At risk of twisting the rules to nearly the point of breaking (if you think this goes too far mods, I apologise and accept that this should be deleted), I'm hoping someone might be able to cast a little light on the following problem regarding hard links to files.
... (6 Replies)
Discussion started by: Smiling Dragon
6 Replies
4. Shell Programming and Scripting
Hello, I am using tcsh on AIX.
I would like to write a script that does the following:
1. given an inode, how do I find exactly the name of the file?
I know I could do this using ls -i | grep <inode>
but it returns: <inode> <filename>. I need some string manipulation or something to... (1 Reply)
Discussion started by: lastZenMaster
1 Replies
5. Shell Programming and Scripting
Hi all,
I am struggling to change the content of a file without changing the inode number. The exact issue is as below.
I have a file name test.bak which has 100 lines of text.
I am trying to to delete the first 90 lines of the text in the file.
I know that using sed/awk/head/tail I can... (3 Replies)
Discussion started by: sathishkmrv
3 Replies
6. Shell Programming and Scripting
i have a requirement where i needed to change variable values in a properties file(first file) whenever there is change to Release details file(second file). My question is do i have to create a daemon process that always checks the modified time/inode change of the second file and then change the... (1 Reply)
Discussion started by: saikiran_1984
1 Replies
7. Red Hat
Hi,
I have created a file abc.log in Redhat Linux.
Inode number for a file get changes every time i update the file using vi editor.
Is there any setting that can be made , such that inode number never gets changed?
Or if we cannot restrict from inode number getting changed , is... (9 Replies)
Discussion started by: raghu.amilineni
9 Replies
8. UNIX for Advanced & Expert Users
Hello all,
I am on hpux itanium 11.31...and we run a oracle DB on it. I am testing some backup and restore situation.... first i select some data from the DB.....now i remove some files from the DB where my data is being selected from.....now i select the same data from the DB but i still get... (5 Replies)
Discussion started by: abdul.irfan2
5 Replies
9. Solaris
Some one please help me to find deleted file name, if I am having inode number in Solaris without using any 3rd party tool.
Thanks :) (3 Replies)
Discussion started by: aksijain
3 Replies
10. Linux
Hi,
I have created a file a.txt in Redhat Linux.
Inode number for a file changes every time i update the file using vi editor , gedit etc.
Is there any setting that can be made , such that inode number never changes as that is supposed to be the expected behavior?
Or if we cannot... (13 Replies)
Discussion started by: srirammanohar
13 Replies
LEARN ABOUT HPUX
clri_hfs
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)