I have another question. if I mount a filesystem on root partition, is inodes on mounted file system is going to be added to root inodes ?

thanks for help

Alain Spineux wrote:

You can get inode info using "df -i" or tune2fs You should get info about journaling info using tune2fs too. Journal size is set a creation time using mke2fs

"man" will help you :-)

On 9/7/07, Centos centos@unixplanet.biz wrote:

...

Hello

what is the limitation of inode and journaling on 32 bit ext3 file system. what about 64 bit.

Thanks

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

On Fri, 2007-09-07 at 14:11 -0700, Scott Silva wrote:

Centos spake the following on 9/7/2007 1:38 PM:

...

I have another question. if I mount a filesystem on root partition, is inodes on mounted file system is going to be added to root inodes ?

If you mean you mount the FS over /, you lose access to the real root when new apps start. A mount "hides" all items under the mounted upon directory. Existing apps may be able to access these hidden ones, I'm not sure, since they have open files in the underlying structures already.

If you mean you are mounting on some directory in the root file system other than /, a very common scenario, there is no problem. As Scott said, FS info is unique to each partition and they are additive *except* as they "hide" everything contained within the directuroy upon which you mount the FS. You effectively lose access to the hidden stuff by *new* processes (unless they inherit open file descriptors for the hidden stuff I think).

...

thanks for help

No. The inodes are part of the underlying partition, and it doesn't matter how many filesystems are nested or how deep. If you have say a var partition under the root partition, and you use all the inodes in the var partition, you can still add files to the rest of the root partition.

-- Bill