12-19-2005
doubts reg inodes
Dear all,
We have a logfile which is written into by a background process running continuously. This logfile size keeps increasing rapidly. While trying to manipulate the file, we deleted the file from the directory. But the process kept on writing into the file and the directory space got filled up.
According to inode concept, the file is not completely removed until the last reference to the inode is gone.
My question is how to trace these inodes which exist even after the files get deleted but a process is working on it.
Please let me know if i am not clear.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Could someone please explain to me the concept of INodes?
Colour me a DOS/MacOS junkie, but I don't quite understand.
Is there any relation to clusters, or physical distro.?
ty. (3 Replies)
Discussion started by: boris888
3 Replies
2. Solaris
Does anyone know what command I can run to check how many inodes are in use on a specific filesystem. On Data General servers I used to run the df -k command to check the status of the inodes for all file system.s (1 Reply)
Discussion started by: soliberus
1 Replies
3. Solaris
hi
i need to find all the files that r linked to the current file as i need to delete the file as well as few of its links :confused:
thnx in advance (1 Reply)
Discussion started by: livemyway
1 Replies
4. UNIX for Dummies Questions & Answers
how is the location of inodes in the physical disk.
are they sequential like:
bootblock|superblock|inode1|inode2| ....| datablock1|datablock2|datablock3
or are they distributed among data blocks like:
bootblock|superblock|inode1|datablock1|inode2|datablock2|datablock3|inode3
|datablock4 (3 Replies)
Discussion started by: gfhgfnhhn
3 Replies
5. Linux
Any good sites, tutorials that explain Inodes clearly and completely ? (3 Replies)
Discussion started by: nitin09
3 Replies
6. Solaris
Hi ,
Can someone help me to increase "inode" in solaris 9?
Thanks in advance,
Gowtham (8 Replies)
Discussion started by: gowthamakanthan
8 Replies
7. Filesystems, Disks and Memory
Hi, sorry to have written in other language i think i could do that.
I would to know
A file system use inodes indexed allocation as a method of allocating space.
In the inode blocks are 10 references to direct, 1 indirect reference to a single block, 1 block indirect reference to a reference to... (1 Reply)
Discussion started by: maryprin
1 Replies
8. Solaris
Dear Forum,
Please help me i have SUNW,Sun-Fire-V240 with sun solaris 8,if i check inode in /var like below:
# df -F ufs -o i
Filesystem iused ifree %iused Mounted on
/dev/md/dsk/d0 62354 310638 17% /
/dev/md/dsk/d3 372992 0 100% /var... (2 Replies)
Discussion started by: fredginting
2 Replies
9. UNIX for Advanced & Expert Users
How can i trace Inode structure and modify it in UNIX kernel?
We want to change the inode structure in the sense that we want to add a new field to the inode data structure. So we want to know how and where to trace inode (7 Replies)
Discussion started by: Group_Inode
7 Replies
10. Shell Programming and Scripting
Hi,
Is there a restriction in the number of inodes a particular directory can have in Solaris.
If so how can we determine that.
Regards (3 Replies)
Discussion started by: @bhi
3 Replies
LEARN ABOUT DEBIAN
logsave
LOGSAVE(8) System Manager's Manual LOGSAVE(8)
NAME
logsave - save the output of a command in a logfile
SYNOPSIS
logsave [ -asv ] logfile cmd_prog [ ... ]
DESCRIPTION
The logsave program will execute cmd_prog with the specified argument(s), and save a copy of its output to logfile. If the containing
directory for logfile does not exist, logsave will accumulate the output in memory until it can be written out. A copy of the output will
also be written to standard output.
If cmd_prog is a single hyphen ('-'), then instead of executing a program, logsave will take its input from standard input and save it in
logfile
logsave is useful for saving the output of initial boot scripts until the /var partition is mounted, so the output can be written to
/var/log.
OPTIONS
-a This option will cause the output to be appended to logfile, instead of replacing its current contents.
-s This option will cause logsave to skip writing to the log file text which is bracketed with a control-A (ASCII 001 or Start of
Header) and control-B (ASCII 002 or Start of Text). This allows progress bar information to be visible to the user on the console,
while not being written to the log file.
-v This option will make logsave to be more verbose in its output to the user.
AUTHOR
Theodore Ts'o (tytso@mit.edu)
SEE ALSO
fsck(8)
E2fsprogs version 1.42.5 July 2012 LOGSAVE(8)