11-12-2008
fd.file-max against inode
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.
Last edited by itik; 11-12-2008 at 08:20 PM..
9 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. 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
3. 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
4. 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
5. 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
6. 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
7. Solaris
Is there any way to create a file on Solaris 10 (ZFS preferably, but UFS would be helpful as well) with a specific inode number? I need to create a file with a large inode, greater than a 32bit integer.
I am trying to test a piece of software which may be incorrectly truncating large inodes down... (16 Replies)
Discussion started by: unblockable
16 Replies
8. 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
9. UNIX for Dummies Questions & Answers
How do you find the maximum file size with the following information -:
A unix filesystem has 1024 bytes block size with 32-bit address. The i-node has 12 direct and 1 indirect, 1 double indirect, and 1 triple indirect addresses. What is the maximum file size it can access ?
What is the... (1 Reply)
Discussion started by: sreyan32
1 Replies
LEARN ABOUT CENTOS
freeze_super
FREEZE_SUPER(9) The Linux VFS FREEZE_SUPER(9)
NAME
freeze_super - lock the filesystem and force it into a consistent state
SYNOPSIS
int freeze_super(struct super_block * sb);
ARGUMENTS
sb
the super to lock
DESCRIPTION
Syncs the super to make sure the filesystem is consistent and calls the fs's freeze_fs. Subsequent calls to this without first thawing the
fs will return -EBUSY.
During this function, sb->s_writers.frozen goes through these values:
SB_UNFROZEN
File system is normal, all writes progress as usual.
SB_FREEZE_WRITE
The file system is in the process of being frozen. New writes should be blocked, though page faults are still allowed. We wait for all
writes to complete and then proceed to the next stage.
SB_FREEZE_PAGEFAULT
Freezing continues. Now also page faults are blocked but internal fs threads can still modify the filesystem (although they should not
dirty new pages or inodes), writeback can run etc. After waiting for all running page faults we sync the filesystem which will clean all
dirty pages and inodes (no new dirty pages or inodes can be created when sync is running).
SB_FREEZE_FS
The file system is frozen. Now all internal sources of fs modification are blocked (e.g. XFS preallocation truncation on inode reclaim).
This is usually implemented by blocking new transactions for filesystems that have them and need this additional guard. After all internal
writers are finished we call ->freeze_fs to finish filesystem freezing. Then we transition to SB_FREEZE_COMPLETE state. This state is
mostly auxiliary for filesystems to verify they do not modify frozen fs.
sb->s_writers.frozen is protected by sb->s_umount.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 FREEZE_SUPER(9)