On Thu, 01 Jun 2017 17:15:29 +0800, Yubin Ruan said:
> Regarding to inode number, I notice that nearly every filesystem has tree
> representation of the inode number:
> 1. on-disk inode number
> 2. in-memory inode number
> 3. VFS inode number
> How are these related? I mean, if they
On Wed, May 31, 2017 at 01:30:59PM -0400, Rik van Riel wrote:
> On Wed, 2017-05-31 at 21:37 +0800, Yubin Ruan wrote:
> > I notice that there is a
> >
> > unsigned long i_ino;
> >
> > in definition of `struct inode' [1], which is the virtual filesystem
> > inode.
> > Does that
On Wed, 2017-05-31 at 21:37 +0800, Yubin Ruan wrote:
> I notice that there is a
>
> unsigned long i_ino;
>
> in definition of `struct inode' [1], which is the virtual filesystem
> inode.
> Does that mean "inode number" and is it used for indexing in the
> system-wide
> inode
On Wed, May 31, 2017 at 08:34:09AM +0100, Okash Khawaja wrote:
>
>
> > On 31 May 2017, at 14:37, Yubin Ruan wrote:
> >
> > I notice that there is a
> >
> >unsigned longi_ino;
> >
> > in definition of `struct inode' [1], which is the virtual filesystem
> On 31 May 2017, at 14:37, Yubin Ruan wrote:
>
> I notice that there is a
>
>unsigned longi_ino;
>
> in definition of `struct inode' [1], which is the virtual filesystem inode.
> Does that mean "inode number" and is it used for indexing in the
I notice that there is a
unsigned long i_ino;
in definition of `struct inode' [1], which is the virtual filesystem inode.
Does that mean "inode number" and is it used for indexing in the system-wide
inode table?
If that is the case, would that limit the number of open