> Blesson Paul writes:
>
> > This is an another doubt related to VFS. I want to know
> > wheather all files are assigned their inode number at the
> > mounting time itself or inodes are assigned to files upon
> > accessing only
>
> That would depend on what type of filesystem you use.
> For
Blesson Paul writes:
This is an another doubt related to VFS. I want to know
wheather all files are assigned their inode number at the
mounting time itself or inodes are assigned to files upon
accessing only
That would depend on what type of filesystem you use.
For ext2, inode
Alexander Viro wrote:
>
> On Mon, 14 May 2001, H. Peter Anvin wrote:
>
> > Correct. At least at one time it used the offset of the directory entry
> > when that particular inode was last "seen" by the kernel... meaning that
> > when it finally dropped out of the inode cache, it would change
On Mon, 14 May 2001, H. Peter Anvin wrote:
> Correct. At least at one time it used the offset of the directory entry
> when that particular inode was last "seen" by the kernel... meaning that
> when it finally dropped out of the inode cache, it would change inode
> numbers. I thought that
Alexander Viro wrote:
>
> On Mon, 14 May 2001, Andreas Dilger wrote:
>
> > Just to clarify, this means that the "inode numbers" reported by an
> > msdos filesystem are a function of the disk-layout itself (i.e. they
> > are determined at mount time), and not numbers created when the file
> > is
On Mon, 14 May 2001, Andreas Dilger wrote:
> Just to clarify, this means that the "inode numbers" reported by an
> msdos filesystem are a function of the disk-layout itself (i.e. they
> are determined at mount time), and not numbers created when the file
> is first accessed (AFAIK).
Wrong.
HPA writes:
> Blesson Paul <[EMAIL PROTECTED]> writes:
> > You misunderstood my question. Let take an example. Let I have a msdos
> > partition. No msdos files has inode numbers, right. Let I mount that
> > msdos partition. Then what happens, That is my question. Will the
> > inode numbers are
Blesson Paul writes:
> This is an another doubt related to VFS. I want to know
> wheather all files are assigned their inode number at the
> mounting time itself or inodes are assigned to files upon
> accessing only
That would depend on what type of filesystem you use.
For ext2, inode numbers
> The inode numbers are "invented" by the MS-DOS filesystem driver. In
> the particular case of the "msdos" driver I believe it uses the
> location of the directory entry (the functional equivalent of the
> inode) on disk.
They are generated basically at random with a uniqueness test and may
Followup to: <[EMAIL PROTECTED]>
By author:Blesson Paul <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Hi J
> You misunderstood my question. Let take an example.
> Let I have a msdos partition. No msdos files has inode numbers, right. Let I
> mount that msdos
Hi J
You misunderstood my question. Let take an example.
Let I have a msdos partition. No msdos files has inode numbers, right. Let I
mount that msdos partition. Then what happens, That is my question. Will the
inode numbers are assigned to all msdos files at mounting time
Blesson Paul wrote:
> Hi
> This is an another doubt related to VFS. I want to know
> wheather all files are assigned their inode number at the mounting time itself
> or inodes are assigned to files upon accessing only
er..
inode numbers are assigned at file creation time.
Blesson Paul wrote:
Hi
This is an another doubt related to VFS. I want to know
wheather all files are assigned their inode number at the mounting time itself
or inodes are assigned to files upon accessing only
er..
inode numbers are assigned at file creation time.
cu
Hi J
You misunderstood my question. Let take an example.
Let I have a msdos partition. No msdos files has inode numbers, right. Let I
mount that msdos partition. Then what happens, That is my question. Will the
inode numbers are assigned to all msdos files at mounting time
Followup to: [EMAIL PROTECTED]
By author:Blesson Paul [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Hi J
You misunderstood my question. Let take an example.
Let I have a msdos partition. No msdos files has inode numbers, right. Let I
mount that msdos partition. Then
The inode numbers are invented by the MS-DOS filesystem driver. In
the particular case of the msdos driver I believe it uses the
location of the directory entry (the functional equivalent of the
inode) on disk.
They are generated basically at random with a uniqueness test and may change
HPA writes:
Blesson Paul [EMAIL PROTECTED] writes:
You misunderstood my question. Let take an example. Let I have a msdos
partition. No msdos files has inode numbers, right. Let I mount that
msdos partition. Then what happens, That is my question. Will the
inode numbers are assigned to
On Mon, 14 May 2001, Andreas Dilger wrote:
Just to clarify, this means that the inode numbers reported by an
msdos filesystem are a function of the disk-layout itself (i.e. they
are determined at mount time), and not numbers created when the file
is first accessed (AFAIK).
Wrong. open
Alexander Viro wrote:
On Mon, 14 May 2001, Andreas Dilger wrote:
Just to clarify, this means that the inode numbers reported by an
msdos filesystem are a function of the disk-layout itself (i.e. they
are determined at mount time), and not numbers created when the file
is first
On Mon, 14 May 2001, H. Peter Anvin wrote:
Correct. At least at one time it used the offset of the directory entry
when that particular inode was last seen by the kernel... meaning that
when it finally dropped out of the inode cache, it would change inode
numbers. I thought that was a
Alexander Viro wrote:
On Mon, 14 May 2001, H. Peter Anvin wrote:
Correct. At least at one time it used the offset of the directory entry
when that particular inode was last seen by the kernel... meaning that
when it finally dropped out of the inode cache, it would change inode
21 matches
Mail list logo
