10-05-2010
Modifying a file without changing inode number
Thank you very much.
This resolves my issue.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
as kernel keeps track of user activities on a file by its INODE number and I node table .
what is the structure of Inode table. and where does this Inode table mapped into?user space or kernel space?
is the Inode Number is fixed for a file till its deletion?
thanks (1 Reply)
Discussion started by: compbug
1 Replies
2. Shell Programming and Scripting
Example:
O o x
What I would like to do is to rename the first column of the above file without affecting the format. The output should look like the following:
Output:
O o x
#! /bin/ksh
cd $HOME/lib/.Lee
#nl = no. of lines.
nl=`grep 'X' ex | wc -l`
#ln = line no.
ln=1 (17 Replies)
Discussion started by: ilak1008
17 Replies
3. UNIX for Advanced & Expert Users
Hi all
when I execute pmap command on one of my daemon process, I am able to see the following output.
Address Kbytes RSS Anon Locked Mode Mapped File
00010000 40 40 - - r-x-- irs026bmd
00028000 56 56 16 - rwx-- irs026bmd
00036000... (3 Replies)
Discussion started by: axes
3 Replies
4. UNIX for Dummies Questions & Answers
How we can know number of inode present in my Disk including free and occupied.
Is there any tool or program to know how much free inode are there in inode free list . (2 Replies)
Discussion started by: mr_deb
2 Replies
5. 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
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. 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
9. Shell Programming and Scripting
is it possible to change the inode value/ file path of a hard link? (2 Replies)
Discussion started by: fhill2
2 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
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)