Traductions en contexte français - anglais

A clone inode is created as a copy of an original inode.

The inode itself may be stored in a file (referred to as the inode file), and the storage may perform updates to the inode file atomically as well.

Stored in each inode are a first identifier and a second identifier.

Each additional file clone created spawns a clone inode.

A new consistency point occurs when the fsinfo block (2440) is updated by writing a new root inode for the inode file (1210) into it.

In this case, there are three files with the same inode number.

The second snapshot includes an inode corresponding to each source file in the second set of files.

Unlike prior art file systems that create a clone by duplicating the entire inode file and all of the indirect blocks, the present invention duplicates only the inode that describes the inode file.

@MiniGod No a symlink is an inode to a block of data that stores a path to another inode (filename).

The first snapshot includes an inode corresponding to each source file in the first set of files.

They're just an additional pointer directly to an inode.

We can have multiple files associated with the same inode.

Each file has an inode and is identified by an inode umber (i-number) in the file system where it resides.

Very small files are in-lined into the inode block.

Each file has an inode and is identified by an inode number (i-number) in the file system where it resides.