Consider a file system implemented using unix inode. The system consist of $n_{0}$ direct disk block addresses, $n_{1}$ single indirect disk block addresses, $n_{2}$ doubly indirect DBAs and $n_{3}$ triple indirect DBAs.
The Disk Block Address = $\text{DBA}$ bits
The Disk Block Size = ${\text{DB}}_{\text{Size}}$ Kbits
What is the total size of file system? Explain how the formula for it holds good.
What is the largest file size possible? Explain how the formula for it holds good.
What is the Maximum possible size of file system? Explain how the formula for it holds good.
This is a description of Unix INODE, from my side:
In a Unix-style file system, the inode is a data structure used to represent a file-system object; which can be one of various things including a file or a directory.
this def. from Wikipedia; the part underlined above seems obscure.
this is how an inode looks like :
to calculate Maximum File Size in the above given question I will use only the triple indirect and obtain 
.
This is so because using one particular Triple Indirect Pointer I can point to this much data at Maximum; A Triple indirect pointer can ultimately point to maximum number of Disk Blocks in comparison to direct/single/double.
and the Total Size of the file system (i.e. how much data we can point to + it excludes file system metadata)
saying this holds good to me coz in this formula all pointers, which INODE has been representing are taken into account.
But I investigated this, asked the GATEOverflow community and found that
If I consider this good then it is making me assume that all other metadata of inode is vanished and only a single disk block is being used completely(something like that) to hold up pointers to other disk blocks. What about single/double/triple indirect pointing phenomenon?
and for the Maximum possible Size of file system = total size of disk on which the file system is implemented. this includes data we can point to + all of metadata together.
Please verify what is correct and what isn't.
